From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Morris de Oryx <morrisdeoryx(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function |
Date: | 2023-06-13 10:27:56 |
Message-ID: | 20230613102756.q2dv4uvxz4slkw4j@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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/
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2023-06-13 10:50:10 | Re: [PATCH] Using named captures in Catalog::ParseHeader() |
Previous Message | John Naylor | 2023-06-13 10:26:23 | Re: [PATCH] Add loongarch native checksum implementation. |