Re: pg_restore error with partitioned table having exclude constraint - Mailing list pgsql-bugs

From Álvaro Herrera
Subject Re: pg_restore error with partitioned table having exclude constraint
Date
Msg-id 202504291453.r37jvblkfqcu@alvherre.pgsql
Whole thread Raw
In response to Re: pg_restore error with partitioned table having exclude constraint  (Japin Li <japinli@hotmail.com>)
Responses Re: pg_restore error with partitioned table having exclude constraint
List 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)



pgsql-bugs by date:

Previous
From: Japin Li
Date:
Subject: Re: pg_restore error with partitioned table having exclude constraint
Next
From: PG Bug reporting form
Date:
Subject: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq