Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints |
| Дата | |
| Msg-id | 202503251152.brshiuib7dfw@alvherre.pgsql обсуждение |
| Ответ на | Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints (Peter Eisentraut <peter@eisentraut.org>) |
| Ответы |
Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
|
| Список | pgsql-hackers |
Hello On 2025-Mar-25, Peter Eisentraut wrote: > A patch in the NOT ENFORCED constraints patch series proposes to refactor > some of the code added by this patch series ([0] patch v18-0001). I noticed > that the code paths from this patch series do not call > InvokeObjectPostAlterHook() or CacheInvalidateRelcache() when a constraint > is altered. Was this intentional? If not, I can fix it as part of that > other patch, just wanted to check here. It was not, I'm good with you fixing it, with thanks. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "The ability of users to misuse tools is, of course, legendary" (David Steele) https://postgr.es/m/11b38a96-6ded-4668-b772-40f992132797@pgmasters.net
В списке pgsql-hackers по дате отправления: