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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: 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-06 03:59:09
Message-ID: CAApHDvpiYnaJ9944g=LJ_impVg6mr9biSgyLgNPNu+KUDDUHcw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 6 Oct 2025 at 16:42, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> I tried to reproduce this, but here is what I see[1] when I dump in
> REL_18_STABLE, I noticed that "NOT NULL a" for inherited tables is
> included along with the create table statement itself, so this doesn't
> seems like an issue, am I missing something?

I think so. I believe the intent was to convey the server version is
17.6 and the pg_dump version is 18.0, in which case, there does appear
to be a problem.

David

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dilip Kumar 2025-10-06 06:22:21 Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
Previous Message Dilip Kumar 2025-10-06 03:42:06 Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases