Horton

Re: not null constraints, again

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

View thread View on postgr.es
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: jian he <jian.universality@gmail.com>
Cc: Tender Wang <tndrwang@gmail.com>, Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-09-24T19:07:14Z
Lists: pgsql-hackers

Attachments

On 2024-Sep-24, Alvaro Herrera wrote:

> I have made these changes and added some tests, and will be posting a v5
> shortly.

I ran the coverage report and found a couple of ereports are not covered
by any tests.  I'm adding those.  May add more tomorrow, after looking
at the coverage report some more.

I should give a try at running Andres' differential coverage report[1]
at some point ...

[1] https://postgr.es/m/20240414223305.m3i5eju6zylabvln%40awork3.anarazel.de

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/

Commits

  1. Suppress "may be used uninitialized" warnings from older compilers.

  2. Elide not-null constraint checks on child tables during PK creation

  3. Remove unnecessary code to handle CONSTR_NOTNULL

  4. Silence compilers about extractNotNullColumn()

  5. Add pg_constraint rows for not-null constraints