Re: BUG #17756: Invalid replica indentity set order in a dump - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17756: Invalid replica indentity set order in a dump
Date
Msg-id 429827.1674229330@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17756: Invalid replica indentity set order in a dump  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17756: Invalid replica indentity set order in a dump  (Sergey Belyashov <sergey.belyashov@gmail.com>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: ST_Union(rast, uniontype) treat bands with different classes as the same as first band
Next
From: Tom Lane
Date:
Subject: Re: BUG #17755: database queries get stuck for certain IDs