From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
---|---|
To: | Japin Li <japinli(at)hotmail(dot)com> |
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-28 08:42:14 |
Message-ID: | 202504280842.2jaxgkldoap2@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2025-Apr-24, Japin Li wrote:
> 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?
Well, there are no tests in the patch. 8c852ba9a434 added some, but
it's now clear that something was overlooked. I think this patch should
make more of an effort to cover all interesting cases in regression
tests if there are holes in coverage; and also add something to verify
that pg_dump and pg_upgrade work correctly for these constraints.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Si quieres ser creativo, aprende el arte de perder el tiempo"
From | Date | Subject | |
---|---|---|---|
Next Message | marcos sicat | 2025-04-28 13:05:28 | Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE |
Previous Message | Pavel Stehule | 2025-04-28 06:17:19 | Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE |