Re: Test instability when pg_dump orders by OID

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Test instability when pg_dump orders by OID
Date: 2025-08-10 17:01:02
Message-ID: CA+TgmoZohCf6+b-VoxpPnfcN-ZHw+GKCiMp8p8Xwx8qN5srgTQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Aug 10, 2025 at 12:37 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> Thanks. Given the current state of freeze for tomorrow's release wrap, the
> decision is less obvious than usual. I'm seeing these options:
>
> 1. Remove the new assertion in v13-v18.
> 2. Push your proposed fix.
> 3. Change nothing. (This would be the choice if one is maximally concerned
> about deviating from the freeze and unconcerned about --enable-cassert
> builds of releases.)
>
> I am inclined to make today's change be (1).

Sounds right to me.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-10 17:10:50 Re: Test instability when pg_dump orders by OID
Previous Message Noah Misch 2025-08-10 16:36:59 Re: Test instability when pg_dump orders by OID