From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Concurrently option for reindexdb |
Date: | 2014-09-01 13:43:40 |
Message-ID: | 5404780C.1000305@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/25/2014 02:36 PM, Sawada Masahiko wrote:
> Hi all,
>
> Attached WIP patch adds "-C (--concurrently)" option for reindexdb
> command for concurrently reindexing.
> If we specify "-C" option with any table then reindexdb do reindexing
> concurrently with minimum lock necessary.
> Note that we cannot use '-s' option (for system catalog) and '-C'
> option at the same time.
> This patch use simple method as follows.
>
> 1. Do "CREATE INDEX CONCURRENTLY" new index which has same definition
> as target index
> 2. Aquire ACCESS EXCLUSIVE LOCK to target table( and transaction starts)
> 3. Swap old and new index
> 4. Drop old index
> 5. COMMIT
How do you handle indexes tied to constraints - PRIMARY KEY, UNIQUE, or
EXCLUSION constraint indexes?
My understanding was that this currently required some less than lovely
catalog hacks.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-09-01 13:45:03 | Re: PL/pgSQL 2 |
Previous Message | Michael Paquier | 2014-09-01 13:41:45 | Re: psql \watch versus \timing |