Re: Alter index rename concurrently to

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Andrey Klychkov <aaklychkov(at)mail(dot)ru>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Alter index rename concurrently to
Date: 2018-07-16 19:19:05
Message-ID: 75C2BE03-A646-4517-A037-703824EE6721@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

> 16 июля 2018 г., в 22:58, Andrey Klychkov <aaklychkov(at)mail(dot)ru> написал(а):
> Dear hackers!
>
> I have an idea to facilitate work with index rebuilding.
> ....
> "ALTER INDEX ... RENAME CONCURRENTLY TO ..."

The idea seems useful. I'm not an expert in CIC, but your post do not cover one very important topic. When we use CREATE INDEX CONCURRENTLY we pay for less intrusive lock by scanning data twice. What is the price of RENAME CONCURRENTLY? Should this mode be default?

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-07-16 19:25:19 Re: [HACKERS] logical decoding of two-phase transactions
Previous Message Andrey Klychkov 2018-07-16 18:58:06 Alter index rename concurrently to