Re: Alter index rename concurrently to

From: Victor Yegorov <vyegorov(at)gmail(dot)com>
To: aaklychkov(at)mail(dot)ru
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Alter index rename concurrently to
Date: 2018-07-16 19:40:33
Message-ID: CAGnEboiyFkmGbQFAvc+tViayyPnbJkWTd93kvmhhML+cQQ_OkA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

пн, 16 июл. 2018 г. в 21:58, Andrey Klychkov <aaklychkov(at)mail(dot)ru>:

> I made a patch to solve this issue (see the attachment).
> It allows to avoid locks by a query like this:
> “alter index <new_index> rename CONCURRENTLY to <old_index_name>”.
>

Please, have a look at previous discussions on the subject:
- 2012
https://www.postgresql.org/message-id/CAB7nPqTys6JUQDxUczbJb0BNW0kPrW8WdZuk11KaxQq6o98PJg@mail.gmail.com
- 2013
https://www.postgresql.org/message-id/CAB7nPqSTFkuc7dZxCDX4HOTU63YXHRroNv2aoUzyD-Zz_8Z_Zg@mail.gmail.com
- https://commitfest.postgresql.org/16/1276/

--
Victor Yegorov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-07-16 20:04:12 Re: Fix some error handling for read() and errno
Previous Message Tomas Vondra 2018-07-16 19:25:19 Re: [HACKERS] logical decoding of two-phase transactions