Re: using index or check in ALTER TABLE SET NOT NULL

Поиск
Список
Период
Сортировка
От Sergei Kornilov
Тема Re: using index or check in ALTER TABLE SET NOT NULL
Дата
Msg-id 53138721541354599@sas1-d856b3d759c7.qloud-c.yandex.net
обсуждение исходный текст
Ответ на Re: using index or check in ALTER TABLE SET NOT NULL  (Dmitry Dolgov <9erthalion6@gmail.com>)
Ответы Re: using index or check in ALTER TABLE SET NOT NULL  (Dmitry Dolgov <9erthalion6@gmail.com>)
Список pgsql-hackers
Hello

> This patch went through the last tree commit fests without any noticeable activity
Well, last two CF. During march commitfest patch has activity and was marked as ready for committer. But at end of july
CFwas no further activity and patch was reverted back to "need review" with reason [1]:
 
> It's not clear that there is consensus that this is wanted.
I can't say something here.

> If not properly cataloguing NOT NULL constraints would be fixed, can it
> potentially conflict with the current patch or not?
We already doing same stuff for "alter table attach partition" and in this patch i use exactly this routine. If proper
cataloguingwould conflict with my patch - it would conflict with "attach partition" validation too.
 
I think proper cataloguing can be implemented without conflict with proposed feature.

regards, Sergei

[1]: https://www.postgresql.org/message-id/c4c7556d-a046-ac29-2549-bdef0078b6fe%402ndQuadrant.com


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

Предыдущее
От: Andreas 'ads' Scherbaum
Дата:
Сообщение: Re: [PATCH] Improvements to "Getting started" tutorial for GoogleCode-in task
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Making all nbtree entries unique by having heap TIDs participatein comparisons