Re: pg_restore error with partitioned table having exclude constraint
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Japin Li <japinli@hotmail.com>
Cc: Keith Paskett <keith.paskett@logansw.com>, pgsql-bugs@lists.postgresql.org
Date: 2025-04-30T10:45:11Z
Lists: pgsql-bugs
On 2025-Apr-30, Japin Li wrote: > Thank you for the explanation. A test case has been added to create_index.sql. > Could you please take a look? Well, it seems a bit minimalistic -- I would try to be more adversarial about it maybe, because details are where devil(s) lie. You need to add comments in CompareIndexInfo about your new code. Why is it okay to ignore ii_ExclusionProcs and ii_ExclusionStrats? Why is it okay to not have tests that set up tables with those things as different so that this function returns false in these cases? Why do you have a test for a table set up where the positive case is handled, but no case for the negative case? -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Allow some exclusion constraints on partitions
- 8c852ba9a434 17.0 cited
-
Local partitioned indexes
- 8b08f7d4820f 11.0 cited