Shouldn't pg_(sh)seclabel.provider be marked NOT NULL?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Shouldn't pg_(sh)seclabel.provider be marked NOT NULL?
Дата
Msg-id 7644.1403283690@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: Shouldn't pg_(sh)seclabel.provider be marked NOT NULL?
Список pgsql-hackers
Some of my Salesforce colleagues are looking into making every system
catalog be declared with a true primary key.  They came across the
fact that pg_seclabel and pg_shseclabel are declared with unique
indexes that include the "provider" column, but that column does not
get marked as NOT NULL during initdb.  Shouldn't it be?  For that
matter, it doesn't look to me like the code intends to ever store
a null value into the label column either --- should that also be
marked NOT NULL?

I think we've generally been lazy about marking variable-width catalog
columns as NOT NULL (note bootstrap mode will mark fixed-width columns
as NOT NULL automatically).  I'm not necessarily arguing to try to clean
this up altogether, but it would be good I think if indexable columns
got marked NOT NULL whenever possible.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: modify custom variables
Следующее
От: Joey Caughey
Дата:
Сообщение: JSON and Postgres Variable Queries