Re: REINDEX CONCURRENTLY and indisreplident

Euler Taveira <euler.taveira@2ndquadrant.com>

From: Euler Taveira <euler.taveira@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-06-03T15:40:38Z
Lists: pgsql-hackers
On Wed, 3 Jun 2020 at 03:54, Michael Paquier <michael@paquier.xyz> wrote:

> Hi all,
>
> I have bumped into $subject, causing a replica identity index to
> be considered as dropped if running REINDEX CONCURRENTLY on it.  This
> means that the old tuple information would get lost in this case, as
> a REPLICA IDENTITY USING INDEX without a dropped index is the same as
> NOTHING.
>
> LGTM. I tested in both versions (12, master) and it works accordingly.


-- 
Euler Taveira                 http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Preserve pg_index.indisreplident across REINDEX CONCURRENTLY