Horton

Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: jian he <jian.universality@gmail.com>, Rushabh Lathia <rushabh.lathia@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-04-25T09:02:07Z
Lists: pgsql-hackers 
On 2025-Apr-23, Nathan Bossart wrote:

> This one was briefly discussed in an RMT meeting.
> 
> On Wed, Apr 09, 2025 at 01:16:20PM +0800, jian he wrote:
> > attached patch is for address pg_dump inconsistency
> > when parent is "not null not valid" while child is "not null".
> 
> I see an open item [0] that points to this patch, but there's no owner
> listed, and there doesn't appear to have been any follow-up discussion.
> Álvaro, should I list you as the owner, and if so, are you planning to look
> at it soon?

Hello, yes, please list me as owner, and now at least there's a patch I
feel more comfortable with :-)  I'll leave it there for a couple of days
for Jian and Rushabh to comment.

Thanks,

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/

Commits

  1. Allow NOT NULL constraints to be added as NOT VALID

  2. Add missing deparsing of [NO] IDENT to XMLSERIALIZE()

  3. backend launchers void * arguments for binary data

  4. Add pg_constraint rows for not-null constraints

  5. Create the infrastructure for planner support functions.

  6. Add prokind column, replacing proisagg and proiswindow