pgsql: Re-think guts of DROP INDEX CONCURRENTLY.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Re-think guts of DROP INDEX CONCURRENTLY.
Date: 2012-10-18 18:04:28
Message-ID: E1TOuSK-0004pJ-AR@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Re-think guts of DROP INDEX CONCURRENTLY.
Concurrent behaviour was flawed when using
a two-step process, so add an additional
phase of processing to ensure concurrency
for both SELECTs and INSERT/UPDATE/DELETEs.

Backpatch to 9.2

Andres Freund, tweaked by me

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/2f0e480d02cde469e64d03dc8ca198cbfd597640

Modified Files
--------------
src/backend/catalog/index.c | 104 +++++++++++++++++++++++++++++++++++++------
1 files changed, 90 insertions(+), 14 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2012-10-18 18:06:20 pgsql: Re-think guts of DROP INDEX CONCURRENTLY.
Previous Message Tom Lane 2012-10-18 16:30:44 pgsql: Fix planning of non-strict equivalence clauses above outer joins