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

From Simon Riggs
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id CA+U5nMJtsRCLAa2WhiXnb5WcJSQFqRRE4ZhnfMv178Lsb6y3pA@mail.gmail.com
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Support for REINDEX CONCURRENTLY  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 8 December 2012 15:14, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Maybe the best way is to admit that we need a short-term exclusive lock
> for the swapping step.

Which wouldn't be so bad if this is just for the toast index, since in
many cases the index itself is completely empty anyway, which must
offer opportunities for optimization.

> Or we could wait for MVCC catalog access ...

If there was a published design for that, it would help believe in it more.

Do you think one exists?

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proof of concept: auto updatable views [Review of Patch]
Next
From: Jan Wieck
Date:
Subject: Re: MySQL search query is not executing in Postgres DB