Update information_schema definition for not-null constraints
commit3af7217942722369a6eb7629e0fb1cbbef889a9b
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Thu, 7 Sep 2023 09:33:01 +0000 (7 11:33 +0200)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Thu, 7 Sep 2023 09:33:01 +0000 (7 11:33 +0200)
tree2ae1564a34f93d7c7e430453cea3f6e0a06467dd
parente1c6db6309292827fc6baf7cf7df87d49254c7e1
Update information_schema definition for not-null constraints

Now that we have catalogued not-null constraints, our information_schema
definition can be updated to grab those rather than fabricate synthetic
definitions.

Note that we still don't have catalog rows for not-null constraints on
domains, but we've never had not-null constraints listed in
information_schema, so that's a problem to be solved separately.

Co-authored-by: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Co-authored-by: Álvaro Herrera <alvherre@alvh.no-ip.org>
Discussion: https://postgr.es/m/81b461c4-edab-5d8c-2f88-203108425340@enterprisedb.com
Discussion: https://postgr.es/m/202309041710.psytrxlsiqex@alvherre.pgsql
src/backend/catalog/information_schema.sql
src/include/catalog/catversion.h