Feedback-ID: ia2694551:Fastmail
Date: Tue, 13 Jun 2023 12:27:56 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Morris de Oryx <morrisdeoryx@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function
Message-ID: <20230613102756.q2dv4uvxz4slkw4j@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKqnccg0KcABGXzPJagc7nE5ePb-yZ6LMCRuD_bf8h04_HRhrA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20230613102756.q2dv4uvxz4slkw4j%40alvherre.pgsql>
Precedence: bulk

On 2023-Jun-13, Morris de Oryx wrote:

> Quick follow-up: I've heard back from AWS regarding applying Tom Lane's
> patch. Nope. RDS releases numbered versions, nothing else.

Sounds like a reasonable policy to me.

> As Postgres is now at 15.8/15.3 in the wild and on 15.7/15.3 on RDS,
> I'm guessing that the patch won't be available until 14.9/15.4.
> 
> Am I right in thinking that this patch will be integrated into 14.9/15.4,

Yes.  The commits got into Postgres on June 4th, and 14.8 and 15.3 where
stamped on May 8th.  So the fixes will be in 14.9 and 15.4 in August,
per https://www.postgresql.org/developer/roadmap/

> if they are released?

No "if" about this, unless everybody here is hit by ICBMs.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/