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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
