pgsql: Force some system catalog table columns to be marked NOT NULL.

Started by Andres Freundover 11 years ago1 messagescomitters

andres@anarazel.de

over 11 years ago

Force some system catalog table columns to be marked NOT NULL.

In a manual pass over the catalog declaration I found a number of
columns which the boostrap automatism didn't mark NOT NULL even though
they actually were. Add BKI_FORCE_NOT_NULL markings to them.

It's usually not critical if a system table column is falsely determined
to be nullable as the code should always catch relevant cases. But it's
good to have a extra layer in place.

Discussion: 20150215170014.GE15326@awork2.anarazel.de

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/82a532b34d7547b43b90e2e4d4953f4be1c655b8

Modified Files
--------------
src/include/catalog/pg_description.h | 2 +-
src/include/catalog/pg_extension.h | 4 ++--
src/include/catalog/pg_largeobject.h | 2 +-
src/include/catalog/pg_pltemplate.h | 4 ++--
src/include/catalog/pg_proc.h | 2 +-
src/include/catalog/pg_seclabel.h | 4 ++--
src/include/catalog/pg_shdescription.h | 2 +-
src/include/catalog/pg_shseclabel.h | 4 ++--
src/include/catalog/pg_trigger.h | 2 +-
9 files changed, 13 insertions(+), 13 deletions(-)

--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers