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
Date: Fri, 20 Jan 2023 10:42:10 -0500
Message-ID: <429827.1674229330@sss.pgh.pa.us> (raw)
In-Reply-To: <17756-dd50e8e0c8dd4a40@postgresql.org>
References: <17756-dd50e8e0c8dd4a40@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, sergey.belyashov@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17756: Invalid replica indentity set order in a dump
In-Reply-To: <429827.1674229330@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox