From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: sergey.belyashov@gmail.com
Subject: BUG #17756: Invalid replica indentity set order in a dump
Date: Fri, 20 Jan 2023 13:41:07 +0000
Message-ID: <17756-dd50e8e0c8dd4a40@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17756
Logged by: Sergey Belyashov
Email address: sergey.belyashov@gmail.com
PostgreSQL version: 14.5
Operating system: Debian Linux x86_64
Description:
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.
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, sergey.belyashov@gmail.com
Subject: Re: BUG #17756: Invalid replica indentity set order in a dump
In-Reply-To: <17756-dd50e8e0c8dd4a40@postgresql.org>
* 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