From: Tom Lane <tgl@sss.pgh.pa.us>
To: sergey.belyashov@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17756: Invalid replica indentity set order in a dump
In-reply-to: <17756-dd50e8e0c8dd4a40@postgresql.org>
References: <17756-dd50e8e0c8dd4a40@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 20 Jan 2023 13:41:07 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <429826.1674229330.1@sss.pgh.pa.us>
Date: Fri, 20 Jan 2023 10:42:10 -0500
Message-ID: <429827.1674229330@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/429827.1674229330%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Some database have a partitioned table with unique index used as REPLICA
> IDENTITY. pg_dump places ALTER TABLE tbl REPLICA IDENTITY USING INDEX
> some_idx after partial index creation. But Postgresql fails to restore such
> dump because replica identity cannot be set on invalid index some_idx:
> partition indices are not created.

Please provide a concrete example, preferably a SQL script to create
a database that triggers the problem.  There are enough variables
here that nobody is likely to be excited about trying to reverse-
engineer a test case from only this amount of detail.

			regards, tom lane