| From: | Japin Li <japinli(at)hotmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Keith Paskett <keith(dot)paskett(at)logansw(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_restore error with partitioned table having exclude constraint |
| Date: | 2025-04-24 15:07:53 |
| Message-ID: | ME0P300MB04459912DFAA3BEC7215C0BEB6852@ME0P300MB0445.AUSP300.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 17 Apr 2025 at 17:18, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> On 2025-Apr-17, Japin Li wrote:
>
>> It seems PG 16 does not support exclusion constraints on partitioned tables.
>
> Yeah, my recollection is that they were purposefully disallowed (mainly
> because I didn't want to research how to fully make them work when
> adding local partitioned indexes), and that we needed to do more work if
> we wanted to let them through. I suspect commit 8c852ba9a4 was mistaken
> to allow that case without looking for further implications.
>
Sorry, I’m unclear on “more work.” Can you explain further?
--
Regrads,
Japin Li
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-04-24 23:31:55 | Re: BUG #18893: Segfault during analyze pg_database |
| Previous Message | Tender Wang | 2025-04-24 13:29:13 | Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c" |