Re: PGQ catalog representation and pg_dump support

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Taha Naveed <m(dot)taha(dot)naveed27(at)gmail(dot)com>, 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 15:47:56
Message-ID: CAExHW5vSJr-gkBcT6BZ2w05+OBPJb_bEyDfNw_Kf7LDbS_-bZw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Aug 23, 2026 at 8:52 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> - GRAPH_TABLE's rewriter enumerates the full cartesian product of
> candidate paths with no bound on breadth. A short EXPLAIN over a
> middling multi-element pattern — SELECT on someone else's graph is
> enough, or
> just the default TEMP privilege — can OOM the backend bringing down
> the postmaster. That one probably belongs first in the queue.
>

This was being discussed at [1]. We will consider it in the next round.

[1] https://www.postgresql.org/message-id/CAEG8a3+4tA=e2M_f=dfaMgur+HJQ4R11v0torj2nc_k8XX3U6A@mail.gmail.com

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Samokhvalov 2026-09-10 16:02:04 PG19: two RI fast-path issues found while testing the batching revert
Previous Message Jim Jones 2026-09-10 15:47:36 Re: Add a permission check to pg_stat_get_backend_subxact()