You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@age.apache.org by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org> on 2025/11/14 17:41:09 UTC
[I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
arthur-valadares-psiquantum opened a new issue, #2245:
URL: https://github.com/apache/age/issues/2245
**Describe the bug**
For some strange reason, at exactly 42 vertex labels the drop_graph starts failing with "label (relation) cache corrupted". Note that the graph still happens, but the connection is returned broken and requires reconnection.
To reproduce you can run the query below that creates 44 vertexes. To see it not fail, remove around 6 and it should not fail on drop_graph
**How are you accessing AGE (Command line, driver, etc.)?**
- DBeaver (JDBC), sqlalchemy
**What data setup do we need to do?**
```pgsql
...
select * from ag_catalog.create_graph('test_labels_direct');
SELECT * from cypher('test_labels_direct', $$
CREATE (a1:Part1 {part_num: '123'}),
(a2:Part2 {part_num: '345'}),
(a3:Part3 {part_num: '456'}),
(a4:Part4 {part_num: '789'}),
(a5:Part5 {part_num: '123'}),
(a6:Part6 {part_num: '345'}),
(a7:Part7 {part_num: '456'}),
(a8:Part8 {part_num: '789'}),
(a9:Part9 {part_num: '123'}),
(a10:Part10 {part_num: '345'}),
(a11:Part11 {part_num: '456'}),
(a12:Part12 {part_num: '789'}),
(a13:Part13 {part_num: '123'}),
(a14:Part14 {part_num: '345'}),
(a15:Part15 {part_num: '456'}),
(a16:Part16 {part_num: '789'}),
(a17:Part17 {part_num: '123'}),
(a18:Part18 {part_num: '345'}),
(a19:Part19 {part_num: '456'}),
(a20:Part20 {part_num: '789'}),
(a21:Part21 {part_num: '123'}),
(a22:Part22 {part_num: '345'}),
(a23:Part23 {part_num: '456'}),
(a24:Part24 {part_num: '789'}),
(a25:Part25 {part_num: '123'}),
(a26:Part26 {part_num: '345'}),
(a27:Part27 {part_num: '456'}),
(a28:Part28 {part_num: '789'}),
(a29:Part29 {part_num: '789'}),
(a30:Part30 {part_num: '123'}),
(a31:Part31 {part_num: '345'}),
(a32:Part32 {part_num: '456'}),
(a33:Part33 {part_num: '789'}),
(a34:Part34 {part_num: '123'}),
(a35:Part35 {part_num: '345'}),
(a36:Part36 {part_num: '456'}),
(a37:Part37 {part_num: '789'}),
(a38:Part38 {part_num: '123'}),
(a39:Part39 {part_num: '345'}),
(a40:Part40 {part_num: '456'}),
(a41:Part41 {part_num: '789'}),
(a42:Part42 {part_num: '345'}),
(a43:Part43 {part_num: '456'}),
(a44:Part44 {part_num: '789'})
$$) as (a agtype);
...
```
**What is the necessary configuration info needed?**
- None
**What is the command that caused the error?**
```pgsql
select * from ag_catalog.drop_graph('test_labels_direct', true);
```
```
2025-11-14 01:50:57.946 UTC [472] ERROR: label (relation) cache corrupted
2025-11-14T01:50:57.946816366Z 2025-11-14 01:50:57.946 UTC [472] FATAL: terminating connection because protocol synchronization was lost
```
**Expected behavior**
Graph should drop with no errors and not break the connection.
**Environment (please complete the following information):**
- Version: Docker image apache/age:dev_snapshot_PG17
**Additional context**
Add any other context about the problem here.
--
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: dev-unsubscribe@age.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3559338957
You got it! thanks for resolving it so quickly, and appreciate all the hard work done in AGE.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544515378
@arthur-valadares-psiquantum -
"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?"
We support **latest** and the **release docker images**, the others are **strictly for development** and **may not work or be stable**; those are not supported. **latest**, if I recall correctly, points to the latest version release. Of which, thank you for reminding me, I need to update that one.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3560064142
> Can I bug you for one more item? Can we rebuild `latest` to include this new change in docker? Otherwise I'll have to maintain my own local image.
The **latest** is based off of the latest, highest branch, release. In this case, **PG17** 1.6.0 Per Apache, that tag can only be a release.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3550214267
@arthur-valadares-psiquantum PR #2248
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3554741667
I've tested PR 2248 - both in my toy example but also going through my 200+ unit tests, half of which are dropping/recreating graph at each run - everything succeeded!
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3559796162
Can I bug you for one more item? Can we rebuild `latest` to include this new change in docker? Otherwise I'll have to maintain my own local image.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544309808
@arthur-valadares-psiquantum I'm using the latest build from the master branch without issue -
```
psql-17.4-5432-pgsql=# create extension age;
CREATE EXTENSION
psql-17.4-5432-pgsql=# load 'age'; set search_path to ag_catalog;
LOAD
SET
psql-17.4-5432-pgsql=# select * from ag_catalog.create_graph('test_labels_direct');
NOTICE: graph "test_labels_direct" has been created
create_graph
--------------
(1 row)
psql-17.4-5432-pgsql=# SELECT * from cypher('test_labels_direct', $$
psql-17.4-5432-pgsql$# CREATE (a1:Part1 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a2:Part2 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a3:Part3 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a4:Part4 {part_num: '789'}),
psql-17.4-5432-pgsql$# (a5:Part5 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a6:Part6 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a7:Part7 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a8:Part8 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a9:Part9 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a10:Part10 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a11:Part11 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a12:Part12 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a13:Part13 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a14:Part14 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a15:Part15 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a16:Part16 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a17:Part17 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a18:Part18 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a19:Part19 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a20:Part20 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a21:Part21 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a22:Part22 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a23:Part23 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a24:Part24 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a25:Part25 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a26:Part26 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a27:Part27 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a28:Part28 {part_num: '789'}),
psql-17.4-5432-pgsql$# (a29:Part29 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a30:Part30 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a31:Part31 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a32:Part32 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a33:Part33 {part_num: '789'}),
psql-17.4-5432-pgsql$#
psql-17.4-5432-pgsql$# (a34:Part34 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a35:Part35 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a36:Part36 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a37:Part37 {part_num: '789'}),
psql-17.4-5432-pgsql$# (a38:Part38 {part_num: '123'}),
psql-17.4-5432-pgsql$# (a39:Part39 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a40:Part40 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a41:Part41 {part_num: '789'}),
psql-17.4-5432-pgsql$# (a42:Part42 {part_num: '345'}),
psql-17.4-5432-pgsql$# (a43:Part43 {part_num: '456'}),
psql-17.4-5432-pgsql$# (a44:Part44 {part_num: '789'})
psql-17.4-5432-pgsql$# $$) as (a agtype);
a
---
(0 rows)
psql-17.4-5432-pgsql=# select * from ag_label;
name | graph | id | kind | relation | seq_name
------------------+-------+----+------+-------------------------------------+-------------------------
_ag_label_vertex | 16994 | 1 | v | test_labels_direct._ag_label_vertex | _ag_label_vertex_id_seq
_ag_label_edge | 16994 | 2 | e | test_labels_direct._ag_label_edge | _ag_label_edge_id_seq
Part1 | 16994 | 3 | v | test_labels_direct."Part1" | Part1_id_seq
Part2 | 16994 | 4 | v | test_labels_direct."Part2" | Part2_id_seq
Part3 | 16994 | 5 | v | test_labels_direct."Part3" | Part3_id_seq
Part4 | 16994 | 6 | v | test_labels_direct."Part4" | Part4_id_seq
Part5 | 16994 | 7 | v | test_labels_direct."Part5" | Part5_id_seq
Part6 | 16994 | 8 | v | test_labels_direct."Part6" | Part6_id_seq
Part7 | 16994 | 9 | v | test_labels_direct."Part7" | Part7_id_seq
Part8 | 16994 | 10 | v | test_labels_direct."Part8" | Part8_id_seq
Part9 | 16994 | 11 | v | test_labels_direct."Part9" | Part9_id_seq
Part10 | 16994 | 12 | v | test_labels_direct."Part10" | Part10_id_seq
Part11 | 16994 | 13 | v | test_labels_direct."Part11" | Part11_id_seq
Part12 | 16994 | 14 | v | test_labels_direct."Part12" | Part12_id_seq
Part13 | 16994 | 15 | v | test_labels_direct."Part13" | Part13_id_seq
Part14 | 16994 | 16 | v | test_labels_direct."Part14" | Part14_id_seq
Part15 | 16994 | 17 | v | test_labels_direct."Part15" | Part15_id_seq
Part16 | 16994 | 18 | v | test_labels_direct."Part16" | Part16_id_seq
Part17 | 16994 | 19 | v | test_labels_direct."Part17" | Part17_id_seq
Part18 | 16994 | 20 | v | test_labels_direct."Part18" | Part18_id_seq
Part19 | 16994 | 21 | v | test_labels_direct."Part19" | Part19_id_seq
Part20 | 16994 | 22 | v | test_labels_direct."Part20" | Part20_id_seq
Part21 | 16994 | 23 | v | test_labels_direct."Part21" | Part21_id_seq
Part22 | 16994 | 24 | v | test_labels_direct."Part22" | Part22_id_seq
Part23 | 16994 | 25 | v | test_labels_direct."Part23" | Part23_id_seq
Part24 | 16994 | 26 | v | test_labels_direct."Part24" | Part24_id_seq
Part25 | 16994 | 27 | v | test_labels_direct."Part25" | Part25_id_seq
Part26 | 16994 | 28 | v | test_labels_direct."Part26" | Part26_id_seq
Part27 | 16994 | 29 | v | test_labels_direct."Part27" | Part27_id_seq
Part28 | 16994 | 30 | v | test_labels_direct."Part28" | Part28_id_seq
Part29 | 16994 | 31 | v | test_labels_direct."Part29" | Part29_id_seq
Part30 | 16994 | 32 | v | test_labels_direct."Part30" | Part30_id_seq
Part31 | 16994 | 33 | v | test_labels_direct."Part31" | Part31_id_seq
Part32 | 16994 | 34 | v | test_labels_direct."Part32" | Part32_id_seq
Part33 | 16994 | 35 | v | test_labels_direct."Part33" | Part33_id_seq
Part34 | 16994 | 36 | v | test_labels_direct."Part34" | Part34_id_seq
Part35 | 16994 | 37 | v | test_labels_direct."Part35" | Part35_id_seq
Part36 | 16994 | 38 | v | test_labels_direct."Part36" | Part36_id_seq
Part37 | 16994 | 39 | v | test_labels_direct."Part37" | Part37_id_seq
Part38 | 16994 | 40 | v | test_labels_direct."Part38" | Part38_id_seq
Part39 | 16994 | 41 | v | test_labels_direct."Part39" | Part39_id_seq
Part40 | 16994 | 42 | v | test_labels_direct."Part40" | Part40_id_seq
Part41 | 16994 | 43 | v | test_labels_direct."Part41" | Part41_id_seq
Part42 | 16994 | 44 | v | test_labels_direct."Part42" | Part42_id_seq
Part43 | 16994 | 45 | v | test_labels_direct."Part43" | Part43_id_seq
Part44 | 16994 | 46 | v | test_labels_direct."Part44" | Part44_id_seq
(46 rows)
psql-17.4-5432-pgsql=# 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)
psql-17.4-5432-pgsql=#
```
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3560649209
Ah ignore that - I just looked at teh releases and I'm seeing the latest release 1.6 for all previous PG versions, so Im sure that will happen once a release goes out for Postgres 18.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum closed issue #2245: Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted"
URL: https://github.com/apache/age/issues/2245
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3559360222
@arthur-valadares-psiquantum yw!
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3549415594
That's great news, appreciate the update.
That seems to track with some of my own AI interaction tools - they have been heavily hinting at connection caches becoming stale, and some combination of slowly removing the labels, dropping the graph, and disposing of the connection engines in sqlalchemy seemed to be working. But a backend/server solution will certainly be more effective.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3560642926
That's a good point - if I wish to stay on 17 but still want that patch that fixes this bug, would I need to get a tagged version docker build that is specific to PostgresSQL 17? Or does this project not maintain stable branch/tag support with hotfixes for older Postgres versions?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544533709
@arthur-valadares-psiquantum `latest` is currently building and will reflect the PG17 1.6.0 version of Apache AGE. It "should" be done in about an hour, but that depends on Docker Hub load.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544543248
That's great - glad we could reproduce it, and thanks for the docker update as well. I'll switch out to latest.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544485735
@arthur-valadares-psiquantum Okay, now that's an error -
psql-17.4-5432-pgsql=# 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.
The connection to the server was lost. Attempting reset: Succeeded.
psql-17.4-5432-pgsql=#
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3549237567
@arthur-valadares-psiquantum Update -
With the help of an AI tool, I found the cause. Or, rather a solution that resolves it. It appears that in flushing the label relation cache, the keys are in the hash, but not the values. This seems due to the way PG forces other processes to "catch up" on finished transactions.
The solution is fairly straightforward and simple to do. However, as there are other hashes flushed this way in AGE, I need to apply this fix to them as well. So, it may take a day or 2 to get the PR ready.
```
...
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)
psql-17.6-5432-pgsql=# select * from ag_label;
name | graph | id | kind | relation | seq_name
------+-------+----+------+----------+----------
(0 rows)
psql-17.6-5432-pgsql=# select * from ag_catalog.create_graph('test_labels_direct');
NOTICE: graph "test_labels_direct" has been created
create_graph
--------------
(1 row)
psql-17.6-5432-pgsql=#
```
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3558847596
@arthur-valadares-psiquantum If this resolves the issues, could you do the honors and close the ticket? :)
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "arthur-valadares-psiquantum (via GitHub)" <gi...@apache.org>.
arthur-valadares-psiquantum commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3560128259
Ah yes, Im using the snapshot_master until the next tagged release, not a problem - living in the edge :)
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3560159453
@arthur-valadares-psiquantum Just keep in mind that once Apache AGE is working with PostgreSQL 18, the master will be changed to that version of PostgreSQL.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2245:
URL: https://github.com/apache/age/issues/2245#issuecomment-3544320448
@arthur-valadares-psiquantum Btw, I built and ran your commands against **PG17** without issue.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org