| From: | Taha Naveed <m(dot)taha(dot)naveed27(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PGQ catalog representation and pg_dump support |
| Date: | 2026-08-23 08:41:50 |
| Message-ID: | CAPTqavL3R9AbnT8qJ_8wdwDiA0p7i_bDz+-xCwGVve1Fn6anZw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I also encountered an issue with pg_get_propgraphdef() and pg_dump.
CREATE TABLE wr (
id int PRIMARY KEY,
x text
);
CREATE PROPERTY GRAPH gwr
VERTEX TABLES (
wr PROPERTIES (wr AS whole)
);
SELECT pg_get_propgraphdef('gwr'::regclass);
ERROR: cache lookup failed for attribute 0 of relation ...
The graph itself works, and the whole row property can be queried through
GRAPH_TABLE. However, pg_dump also fails because it calls
pg_get_propgraphdef().
Reproduced this on PG 19beta3 as well as current master.
Regards,
Taha
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-08-23 09:13:27 | Re: injection_points: canceled or terminated waiters leak their wait slots |
| Previous Message | Zhijie Hou (Fujitsu) | 2026-08-23 08:15:36 | RE: Proposal: Conflict log history table for Logical Replication |