REINDEX CONCURRENTLY and indisreplident - Mailing list pgsql-hackers

From Michael Paquier
Subject REINDEX CONCURRENTLY and indisreplident
Date
Msg-id 20200603065340.GK89559@paquier.xyz
Whole thread Raw
Responses Re: REINDEX CONCURRENTLY and indisreplident  (Euler Taveira <euler.taveira@2ndquadrant.com>)
List pgsql-hackers
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.

Attached is a fix for this issue, that needs a backpatch down to 12.
Thanks,
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: Default gucs for EXPLAIN
Next
From: Amit Langote
Date:
Subject: Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.