Re: Catalog domain not-null constraints

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Catalog domain not-null constraints
Дата
Msg-id 96cefb54-61e5-45d8-b94b-da57fc1b1b92@eisentraut.org
обсуждение исходный текст
Ответ на Re: Catalog domain not-null constraints  (Aleksander Alekseev <aleksander@timescale.com>)
Ответы Re: Catalog domain not-null constraints  (vignesh C <vignesh21@gmail.com>)
Список pgsql-hackers
On 23.11.23 14:13, Aleksander Alekseev wrote:
> =# create domain connotnull1 integer;
> =# create domain connotnull2 integer;
> =# alter domain connotnull1 add not null value;
> =# alter domain connotnull2 set not null;
> =# \dD
> ERROR:  unexpected null value in cached tuple for catalog
> pg_constraint column conkey

Yeah, for domain not-null constraints pg_constraint.conkey is indeed 
null.  Should we put something in there?

Attached is an updated patch that avoids the error by taking a separate 
code path for domain constraints in ruleutils.c.  But maybe there is 
another way to arrange this.
Вложения

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

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Memory consumed by paths during partitionwise join planning
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Testing autovacuum wraparound (including failsafe)