Re: PGQ catalog representation and pg_dump support

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, rmt(at)lists(dot)postgresql(dot)org
Subject: Re: PGQ catalog representation and pg_dump support
Date: 2026-09-03 20:53:38
Message-ID: 96b179ff-0be2-4467-8fd7-f3afae8d360b@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02.09.26 21:29, Melanie Plageman wrote:
> As such, unless we are misunderstanding something about the
> discussion, we feel it would be better to revert this in 19. That
> would take off the time pressure now and would make it easier to fix
> these things properly in 20 without having to be burdened by backwards
> compatibility and backpatching.

Ok, let's do it.

For clarification: Revert from REL_19_STABLE only, or also from master?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-09-03 20:58:01 Re: [PATCH] Release replication slot on error in SQL-callable slot functions
Previous Message Peter Eisentraut 2026-09-03 20:39:35 Re: WAIT FOR NO_THROW option could use some documentation