Postgres Pro
Downloads
Home   >   mailing lists

[BUGS] BUG #14768: CREATE INDEX CONCURRENTLY IF NOT EXISTS cancelsautovacuum even if the index already exists. - Mailing list pgsql-bugs

From mba.ogolny@gmail.com
Subject [BUGS] BUG #14768: CREATE INDEX CONCURRENTLY IF NOT EXISTS cancelsautovacuum even if the index already exists.
Date
Msg-id 20170802103952.8425.5477@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #14768: CREATE INDEX CONCURRENTLY IF NOT EXISTScancels autovacuum even if the index already exists.  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Tree view 
The following bug has been logged on the website:

Bug reference:      14768
Logged by:          Marcin Barczyński
Email address:      mba.ogolny@gmail.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.


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: rajeshkmr921@gmail.com
Date:
Subject: [BUGS] BUG #14767: Timed out waiting for server startup
Next
From: "Daniel Verite"
Date:
Subject: Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values