Re: Make PG's "NOT NULL"s and attnotnull ("is_nullable") conform to SQL-2011
Vitaly Burovoy <vitaly.burovoy@gmail.com>
From: Vitaly Burovoy <vitaly.burovoy@gmail.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-02-08T09:40:38Z
Lists: pgsql-hackers
Attachments
- catalog-notnull-2-c477e84_cleaned.patch (application/octet-stream) patch
On 2/7/16, Vitaly Burovoy <vitaly.burovoy@gmail.com> wrote: > Hello, Hackers! > > TODO list has an entry "Move NOT NULL constraint information to > pg_constraint" with four links and without two with the newest > work[1][2]. > > I rebased the patch from [2] (in attachment). At least it applies > cleanly on top of c477e84fe2471cb675234fce75cd6bb4bc2cf481 and does > not generate a core dump during "make check". There are no tests for > it and it fails "make check" (by difference) which leads inability to > run "make check-world". It seems the file I attached has more than necessary changes. Please, find a correct patch attached. > === > [1]http://www.postgresql.org/message-id/flat/1343682669-sup-2532@alvh.no-ip.org > [2]http://www.postgresql.org/message-id/20160109030002.GA671800@alvherre.pgsql -- Best regards, Vitaly Burovoy
Commits
-
Catalog NOT NULL constraints
- e056c557aef4 16.0 landed
-
Improve documentation about PRIMARY KEY constraints.
- c477e84fe247 9.6.0 cited