Feedback-ID: ie3de48e3:Fastmail
Date: Tue, 29 Apr 2025 16:53:52 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Japin Li <japinli@hotmail.com>
Cc: Keith Paskett <keith.paskett@logansw.com>,
	pgsql-bugs@lists.postgresql.org
Subject: Re: pg_restore error with partitioned table having exclude constraint
Message-ID: <202504291453.r37jvblkfqcu@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <ME0P300MB044557324719C06120ACBC2EB6802@ME0P300MB0445.AUSP300.PROD.OUTLOOK.COM>
Archived-At: 
 <https://www.postgresql.org/message-id/202504291453.r37jvblkfqcu%40alvherre.pgsql>
Precedence: bulk

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)