Re: Dump-restore loosing 'attnotnull' bit for DEFERRABLE PRIMARY KEY column(s).
От | Alvaro Herrera |
---|---|
Тема | Re: Dump-restore loosing 'attnotnull' bit for DEFERRABLE PRIMARY KEY column(s). |
Дата | |
Msg-id | 202405141511.2c653rs3uxks@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: Dump-restore loosing 'attnotnull' bit for DEFERRABLE PRIMARY KEY column(s). (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Dump-restore loosing 'attnotnull' bit for DEFERRABLE PRIMARY KEY column(s).
|
Список | pgsql-hackers |
On 2024-May-14, Robert Haas wrote: > On Tue, May 14, 2024 at 10:42 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > This had already been committed as 270af6f0df76 (the day before it was > > sent to the next commitfest). This commit wasn't included in the > > reverted set, though, so you still get deferrable PKs from > > RelationGetIndexList. I don't think this is necessarily a bad thing, > > though these don't have any usefulness as things stand (and if we deal > > with PKs by forcing not-null constraints to be underneath, then we won't > > need them either). > > So, are you saying this should be marked Committed in the commitfest? Yeah. I've done so. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Pero la cosa no es muy grave ..." (le petit Nicolas -- René Goscinny)
В списке pgsql-hackers по дате отправления: