Re: REINDEX CONCURRENTLY and indisreplident - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: REINDEX CONCURRENTLY and indisreplident
Date
Msg-id CAH503wDaejzhP7+wA-hHS6c7NzE69oWqe5Zf_TYFu1epAwp6EQ@mail.gmail.com
Whole thread Raw
In response to REINDEX CONCURRENTLY and indisreplident  (Michael Paquier <michael@paquier.xyz>)
Responses Re: REINDEX CONCURRENTLY and indisreplident
List 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

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: significant slowdown of HashAggregate between 9.6 and 10
Next
From: Pavel Stehule
Date:
Subject: Re: significant slowdown of HashAggregate between 9.6 and 10