Re: REINDEX CONCURRENT? - Mailing list pgsql-general

From David Rowley
Subject Re: REINDEX CONCURRENT?
Date
Msg-id CAKJS1f_xMao--uZb_v3D5U_8BObhGLVKwCosBthM=oys4CpbKw@mail.gmail.com
Whole thread Raw
In response to REINDEX CONCURRENT?  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
On 9 November 2018 at 17:05, Ron <ronljohnsonjr@gmail.com> wrote:
> Is this very useful feature on the TODO list, and high enough that it might
> get into v12?  (Indexes supporting PK and FK constraints just can't be
> dropped to use CREATE INDEX CONCURRENT.)

There is a patch [1] in the current commitfest which allows indexes to
be renamed without taking an access exclusive lock.  That's a sort of
precursor to allowing REINDEX CONCURRENTLY as, although we can build
indexes without blocking, we can't rename them and it's not much good
if you do a reindex and the new index appears with some other random
name.  If that patch gets in with a good amount of time to spare then
there's a decent chance we'd see a reindex concurrently command patch
appear soon after.

[1] https://commitfest.postgresql.org/20/1726/

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Ron
Date:
Subject: REINDEX CONCURRENT?
Next
From: Karsten Hilbert
Date:
Subject: FIXED: backend crash on DELETE, reproducible locally