Re: REINDEX CONCURRENTLY and indisreplident

From: Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REINDEX CONCURRENTLY and indisreplident
Date: 2020-06-03 15:40:38
Message-ID: CAH503wDaejzhP7+wA-hHS6c7NzE69oWqe5Zf_TYFu1epAwp6EQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 3 Jun 2020 at 03:54, Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2020-06-03 15:43:08 Re: significant slowdown of HashAggregate between 9.6 and 10
Previous Message Pavel Stehule 2020-06-03 15:32:47 significant slowdown of HashAggregate between 9.6 and 10