arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544445243
Thank you @jrgemignani, I thought the docker images were supported. I saw
that `latest` docker image was just as old as the dev_snapshot_PG17, so I've
been assuming that latest does not have support for PG17, so I guess docker
images are just outdated I imagine?
So I repeated the same commands using psql like you did, here's the
interesting thing - you won't notice that postgres crashed your connection
unless you went to look at the logs OR you tried running another command right
after. Notice in my log snippet below, towards the end how running drop_graph
did not crash it - but the next command did. Before running that new
create_graph command I went to look at the logs and I saw the error message.
Anyways - if this is no longer an issue feel free to close this bug report.
I can build my own docker image in `main` branch eventually and retest it. I
appreciate your time to check it!
```
psql (17.5, server 17.6 (Debian 17.6-1.pgdg13+1))
Type "help" for help.
my_db=# create extension age;
ERROR: extension "age" already exists
my_db=# load 'age';
LOAD
my_db=# set search_path to ag_catalog;
SET
my_db=# select * from ag_catalog.create_graph('test_labels_direct');
NOTICE: graph "test_labels_direct" has been created
create_graph
--------------
(1 row)
my_db=# SELECT * from cypher('test_labels_direct', $$
my_db$# CREATE (a1:Part1 {part_num: '123'}),
my_db$# (a2:Part2 {part_num: '345'}),
my_db$# (a3:Part3 {part_num: '456'}),
my_db$# (a4:Part4 {part_num: '789'}),
my_db$# (a5:Part5 {part_num: '123'}),
my_db$# (a6:Part6 {part_num: '345'}),
my_db$# (a7:Part7 {part_num: '456'}),
my_db$# (a8:Part8 {part_num: '789'}),
my_db$#
my_db$# (a9:Part9 {part_num: '123'}),
my_db$# (a10:Part10 {part_num: '345'}),
my_db$# (a11:Part11 {part_num: '456'}),
my_db$# (a12:Part12 {part_num: '789'}),
my_db$#
my_db$# (a13:Part13 {part_num: '123'}),
my_db$# (a14:Part14 {part_num: '345'}),
my_db$# (a15:Part15 {part_num: '456'}),
my_db$# (a16:Part16 {part_num: '789'}),
my_db$#
my_db$# (a17:Part17 {part_num: '123'}),
my_db$# (a18:Part18 {part_num: '345'}),
my_db$# (a19:Part19 {part_num: '456'}),
my_db$# (a20:Part20 {part_num: '789'}),
my_db$#
my_db$# (a21:Part21 {part_num: '123'}),
my_db$# (a22:Part22 {part_num: '345'}),
my_db$# (a23:Part23 {part_num: '456'}),
my_db$# (a24:Part24 {part_num: '789'}),
my_db$#
my_db$# (a25:Part25 {part_num: '123'}),
my_db$# (a26:Part26 {part_num: '345'}),
my_db$# (a27:Part27 {part_num: '456'}),
my_db$# (a28:Part28 {part_num: '789'}),
my_db$# (a29:Part29 {part_num: '789'}),
my_db$#
my_db$# (a30:Part30 {part_num: '123'}),
my_db$# (a31:Part31 {part_num: '345'}),
my_db$# (a32:Part32 {part_num: '456'}),
my_db$# (a33:Part33 {part_num: '789'}),
my_db$#
my_db$# (a34:Part34 {part_num: '123'}),
my_db$# (a35:Part35 {part_num: '345'}),
my_db$# (a36:Part36 {part_num: '456'}),
my_db$# (a37:Part37 {part_num: '789'}),
my_db$# (a38:Part38 {part_num: '123'}),
my_db$# (a39:Part39 {part_num: '345'}),
my_db$# (a40:Part40 {part_num: '456'}),
my_db$# (a41:Part41 {part_num: '789'}),
my_db$# (a42:Part42 {part_num: '345'}),
my_db$# (a43:Part43 {part_num: '456'}),
my_db$# (a44:Part44 {part_num: '789'})
my_db$# $$) as (a agtype);
a
---
(0 rows)
my_db=# select * from ag_label;
my_db=# select * from ag_catalog.drop_graph('test_labels_direct', true);
NOTICE: drop cascades to 46 other objects
DETAIL: drop cascades to table test_labels_direct._ag_label_vertex
drop cascades to table test_labels_direct._ag_label_edge
drop cascades to table test_labels_direct."Part1"
drop cascades to table test_labels_direct."Part2"
drop cascades to table test_labels_direct."Part3"
drop cascades to table test_labels_direct."Part4"
drop cascades to table test_labels_direct."Part5"
drop cascades to table test_labels_direct."Part6"
drop cascades to table test_labels_direct."Part7"
drop cascades to table test_labels_direct."Part8"
drop cascades to table test_labels_direct."Part9"
drop cascades to table test_labels_direct."Part10"
drop cascades to table test_labels_direct."Part11"
drop cascades to table test_labels_direct."Part12"
drop cascades to table test_labels_direct."Part13"
drop cascades to table test_labels_direct."Part14"
drop cascades to table test_labels_direct."Part15"
drop cascades to table test_labels_direct."Part16"
drop cascades to table test_labels_direct."Part17"
drop cascades to table test_labels_direct."Part18"
drop cascades to table test_labels_direct."Part19"
drop cascades to table test_labels_direct."Part20"
drop cascades to table test_labels_direct."Part21"
drop cascades to table test_labels_direct."Part22"
drop cascades to table test_labels_direct."Part23"
drop cascades to table test_labels_direct."Part24"
drop cascades to table test_labels_direct."Part25"
drop cascades to table test_labels_direct."Part26"
drop cascades to table test_labels_direct."Part27"
drop cascades to table test_labels_direct."Part28"
drop cascades to table test_labels_direct."Part29"
drop cascades to table test_labels_direct."Part30"
drop cascades to table test_labels_direct."Part31"
drop cascades to table test_labels_direct."Part32"
drop cascades to table test_labels_direct."Part33"
drop cascades to table test_labels_direct."Part34"
drop cascades to table test_labels_direct."Part35"
drop cascades to table test_labels_direct."Part36"
drop cascades to table test_labels_direct."Part37"
drop cascades to table test_labels_direct."Part38"
drop cascades to table test_labels_direct."Part39"
drop cascades to table test_labels_direct."Part40"
drop cascades to table test_labels_direct."Part41"
drop cascades to table test_labels_direct."Part42"
drop cascades to table test_labels_direct."Part43"
drop cascades to table test_labels_direct."Part44"
NOTICE: graph "test_labels_direct" has been dropped
drop_graph
------------
(1 row)
my_db=#
my_db=#
my_db=#
my_db=#
my_db=# select * from ag_catalog.create_graph('test_labels_direct');
ERROR: label (relation) cache corrupted
FATAL: terminating connection because protocol synchronization was lost
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]