Re: Preserve attstattarget on REINDEX CONCURRENTLY

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ronan Dunklau <ronan(at)dunklau(dot)fr>
Cc: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Preserve attstattarget on REINDEX CONCURRENTLY
Date: 2021-02-05 07:43:44
Message-ID: YBz3MDg2ocZuFh1p@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 05, 2021 at 08:22:17AM +0100, Ronan Dunklau wrote:
> I'm not surprised by this answer, the good news is it's being back-patched.

Yes, I have no problem with that. Until this gets fixed, the damage
can be limited with an extra ALTER INDEX, that takes a
ShareUpdateExclusiveLock so there is no impact on the concurrent
activity.

> Looks good to me ! Thank you.

Thanks for looking at it. Tomas, do you have any comments?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kasahara Tatsuhito 2021-02-05 07:52:53 There doesn't seem to be any case where PQputCopyEnd() returns 0
Previous Message Ronan Dunklau 2021-02-05 07:22:17 Re: Preserve attstattarget on REINDEX CONCURRENTLY