Re: Support for REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id CA+U5nM+4StaXH-kHBG9jJaZ3akk2ss4zAWMHyqjzR2u2P1rm+w@mail.gmail.com
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Support for REINDEX CONCURRENTLY  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Support for REINDEX CONCURRENTLY  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 7 December 2012 12:37, Michael Paquier <michael.paquier@gmail.com> wrote:

> There are still two things that are missing in this patch, but I would like
> to have more feedback before moving forward:
> - REINDEX CONCURRENTLY needs tests in src/test/isolation

Yes, it needs those

> - There is still a problem with toast indexes. If the concurrent reindex of
> a toast index fails for a reason or another, pg_relation will finish with
> invalid toast index entries. I am still wondering about how to clean up
> that. Any ideas?

Build another toast index, rather than reindexing the existing one,
then just use the new oid.

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



pgsql-hackers by date:

Previous
From: Amit kapila
Date:
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade problem with invalid indexes