REINDEX CONCURRENTLY and indisreplident

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: REINDEX CONCURRENTLY and indisreplident
Date: 2020-06-03 06:53:40
Message-ID: 20200603065340.GK89559@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
reindex-conc-replident.patch text/x-diff 2.9 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2020-06-03 07:14:38 Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.
Previous Message Guillaume Lelarge 2020-06-03 06:51:10 Re: Default gucs for EXPLAIN