BUG #14768: CREATE INDEX CONCURRENTLY IF NOT EXISTS cancels autovacuum even if the index already exists.

From: mba(dot)ogolny(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Cc: mba(dot)ogolny(at)gmail(dot)com
Subject: BUG #14768: CREATE INDEX CONCURRENTLY IF NOT EXISTS cancels autovacuum even if the index already exists.
Date: 2017-08-02 10:39:52
Message-ID: 20170802103952.8425.5477@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14768
Logged by: Marcin Barczyński
Email address: mba(dot)ogolny(at)gmail(dot)com
PostgreSQL version: 9.6.3
Operating system: Ubuntu 14.04 but most probably it doesn't matter
Description:

I am perfectly aware of the fact that CREATE INDEX CONCURRENTLY on a table
cancels a running autovacuum process on that table.
But CREATE INDEX CONCURRENTLY IF NOT EXISTS should take
ShareUpdateExclusiveLock only after checking that the index doesn't exist.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Verite 2017-08-02 12:00:49 Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Previous Message rajeshkmr921 2017-08-02 07:33:48 BUG #14767: Timed out waiting for server startup