pgsql: In initdb, defend against assignment of NULL values to not-null

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: In initdb, defend against assignment of NULL values to not-null
Date: 2017-06-13 14:54:52
Message-ID: E1dKnDY-0000FV-TM@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

In initdb, defend against assignment of NULL values to not-null columns.

Previously, you could write _null_ in a BKI DATA line for a column that's
supposed to be NOT NULL and initdb would let it pass, probably breaking
subsequent accesses to the row. No doubt the original coding overlooked
this simple sanity check because in the beginning we didn't have any way
to mark catalog columns NOT NULL at initdb time.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b74701043e396a93f1f18098044741daaf75f761

Modified Files
--------------
src/backend/bootstrap/bootstrap.c | 5 +++++
1 file changed, 5 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-06-13 14:57:20 Re: pgsql: Fix collprovider of predefined collations
Previous Message Peter Eisentraut 2017-06-13 14:54:20 pgsql: Fix typo