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:06:20
Message-ID: E1TOuU8-0004td-EP@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
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/5da1c4b7cc46af5d54912447ee51332d1dbd681c

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:43:11 pgsql: Isolation test for DROP INDEX CONCURRENTLY
Previous Message Simon Riggs 2012-10-18 18:04:28 pgsql: Re-think guts of DROP INDEX CONCURRENTLY.