Re: PGQ catalog representation and pg_dump support

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Taha Naveed <m(dot)taha(dot)naveed27(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PGQ catalog representation and pg_dump support
Date: 2026-09-10 09:44:22
Message-ID: CAExHW5tzHXn1K3NEaBxh2N1SW6ZchsGuvmLHYUXHDbFjYw81PQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Aug 23, 2026 at 2:12 PM Taha Naveed <m(dot)taha(dot)naveed27(at)gmail(dot)com> wrote:
>
> 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.

Agreed this is an issue. The fix is to use get_target_list() to
deparse the PROPERTIES clause. I have a patch for this. Will post when
SQL/PGQ is resurrected.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mailinglists 2026-09-10 09:47:31 unexpected behaviour generating queryid
Previous Message David Geier 2026-09-10 09:43:04 Reducing relcache memory usage 2: shrink sizeof(RelationData)