Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Andrew Bille <andrewbille(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
Date: 2025-10-17 20:50:30
Message-ID: 202510172049.2yfmpkb7al74@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2025-Oct-17, Andrew Bille wrote:

> Looks good for me. I checked it on my enhanced upgrade test.

Cool, thanks for checking.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"No necesitamos banderas
No reconocemos fronteras" (Jorge González)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2025-10-17 21:25:25 Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Previous Message Yuri Zamyatin 2025-10-17 20:09:00 Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade