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

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, andrewbille(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-20 02:30:26
Message-ID: CAFiTN-sX4PuhHYNyXvzvjzEoHsWwcyU9hJ_tKNu-ZB_frCQvnw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, 18 Oct 2025 at 9:52 PM, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:

> On 2025-Oct-06, Dilip Kumar wrote:
>
> > I think we can fix it in getTableAttrs(), see attached, with that I
> > can see my dump is correct. This is just a quick way to show what I
> > am thinking, maybe we can improve this condition.
>
> Pushed, thanks. I added a test so that cross-version upgrade will hit
> this.

Thanks Alvaro!

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message badfilez@gmail.com 2025-10-20 08:51:04 Re: PG17.6 zstd handling bug
Previous Message David Rowley 2025-10-20 01:33:35 Re: Potential "AIO / io workers" inter-worker locking issue in PG18?