Re: CREATE TABLE/ProcessUtility hook behavior change
От | jian he |
---|---|
Тема | Re: CREATE TABLE/ProcessUtility hook behavior change |
Дата | |
Msg-id | CACJufxHUkC5cWDz2mmRTgoo9B=bRyxGLr=QyJ9KQNxeNkdvu0A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: CREATE TABLE/ProcessUtility hook behavior change (David Steele <david@pgmasters.net>) |
Ответы |
Re: CREATE TABLE/ProcessUtility hook behavior change
|
Список | pgsql-hackers |
On Tue, Apr 30, 2024 at 4:35 PM David Steele <david@pgmasters.net> wrote: > > On 4/30/24 12:57, jian he wrote: > > On Tue, Apr 30, 2024 at 10:26 AM David Steele <david@pgmasters.net> wrote: > >> > >> Since bb766cde cannot be readily applied to older commits in master I'm > >> unable to continue bisecting to find the ALTER TABLE behavioral change. > >> > >> This seems to leave me with manual code inspection and there have been a > >> lot of changes in this area, so I'm hoping somebody will know why this > >> ALTER TABLE change happened before I start digging into it. > > I just tested these two commits. https://git.postgresql.org/cgit/postgresql.git/commit/?id=3da13a6257bc08b1d402c83feb2a35450f988365 https://git.postgresql.org/cgit/postgresql.git/commit/?id=b0e96f311985bceba79825214f8e43f65afa653a i think it's related to the catalog not null commit. it will alter table and add not null constraint internally (equivalent to `alter table test alter id set not null`).
В списке pgsql-hackers по дате отправления: