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-29T14:53:52Z
Lists: pgsql-bugs
On 2025-Apr-29, Japin Li wrote:

> My understanding, based on the src/bin/pg_dump tests, is that they don't
> involve a genuine restore of the dumped data to a database.  Instead, it
> dumps to a file using pg_restore.   Is that correct?

Yes.

> I doubt whether I can add a test to pg_dump that would cover this issue.

The pg_upgrade now includes a roundtrip dump/restore which you can take
advantage of.  You just need to ensure some of the src/test/regress/sql
files leave an object in the state you need, and the pg_upgrade test
will run those tests and try to dump and restore the resulting database.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Debido a que la velocidad de la luz es mucho mayor que la del sonido,
 algunas personas nos parecen brillantes un minuto antes
 de escuchar las pelotudeces que dicen." (Roberto Fontanarrosa)



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Allow some exclusion constraints on partitions

  2. Local partitioned indexes