| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Date: | 2024-04-29 18:00:01 |
| Message-ID: | c45f4c95-0cf7-d0f7-189a-d2d87faec229@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-04-29 18:04:41 | Re: Direct SSL connection with ALPN and HBA rules |
| Previous Message | Heikki Linnakangas | 2024-04-29 17:56:42 | Re: Direct SSL connection and ALPN loose ends |