Re: using index or check in ALTER TABLE SET NOT NULL
От | Tom Lane |
---|---|
Тема | Re: using index or check in ALTER TABLE SET NOT NULL |
Дата | |
Msg-id | 7254.1552496972@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: using index or check in ALTER TABLE SET NOT NULL (Sergei Kornilov <sk@zsrv.org>) |
Ответы |
Re: using index or check in ALTER TABLE SET NOT NULL
Re: using index or check in ALTER TABLE SET NOT NULL Re: using index or check in ALTER TABLE SET NOT NULL |
Список | pgsql-hackers |
Sergei Kornilov <sk@zsrv.org> writes: >> Ugh, I guess so. Or how about changing the message itself to use >> INFO, like we already do in QueuePartitionConstraintValidation? > Fine for me. But year ago this was implemented in my patch and Tom voted against using INFO level for such purpose: https://www.postgresql.org/message-id/1142.1520362313%40sss.pgh.pa.us What I thought then was that you didn't need the message at all, at any debug level. I still think that. It might have been useful for development purposes but it does not belong in committed code. INFO (making it impossible for anybody to not have the message in-their-face) is right out. regards, tom lane
В списке pgsql-hackers по дате отправления: