Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
От | Alexander Lakhin |
---|---|
Тема | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
Дата | |
Msg-id | c45f4c95-0cf7-d0f7-189a-d2d87faec229@gmail.com обсуждение исходный текст |
Ответ на | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands (Dmitry Koval <d.koval@postgrespro.ru>) |
Ответы |
Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
|
Список | pgsql-hackers |
Hi Dmitry, 19.04.2024 02:26, Dmitry Koval wrote: > > 18.04.2024 19:00, Alexander Lakhin wrote: >> leaves a strange constraint: >> \d+ t* >> Table "public.tp_0" >> ... >> Not-null constraints: >> "merge-16385-26BCB0-tmp_i_not_null" NOT NULL "i" > > Thanks! > Attached fix (with test) for this case. > The patch should be applied after patches > v6-0001- ... .patch ... v6-0004- ... .patch I still wonder, why that constraint (now with a less questionable name) is created during MERGE? That is, before MERGE, two partitions have only PRIMARY KEY indexes, with no not-null constraint, and you can manually remove the constraint after MERGE, so maybe it's not necessary... Best regards, Alexander
В списке pgsql-hackers по дате отправления: