Thread: BUG #7589: Canceled "CREATE UNIQUE INDEX CONCURRENTLY" leave not-fully-build index existing
BUG #7589: Canceled "CREATE UNIQUE INDEX CONCURRENTLY" leave not-fully-build index existing
From
serovov+pgsql@gmail.com
Date:
The following bug has been logged on the website: Bug reference: 7589 Logged by: Oleg Email address: serovov+pgsql@gmail.com PostgreSQL version: 9.1.6 Operating system: CentOs Description: = See sql console: = 01=3D# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id); ERROR: canceling statement due to statement timeout 01=3D# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id); 01=3D# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id); ERROR: relation "obj_pkey" already exists 01=3D# SELECT version(); PostgreSQL 9.1.6 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-52), 64-bit (1 row)
Re: BUG #7589: Canceled "CREATE UNIQUE INDEX CONCURRENTLY" leave not-fully-build index existing
From
Tom Lane
Date:
serovov+pgsql@gmail.com writes: > 01=# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id); > ERROR: canceling statement due to statement timeout > 01=# CREATE UNIQUE INDEX CONCURRENTLY obj_pkey ON obj (id); > ERROR: relation "obj_pkey" already exists This is not a bug, it is the documented failure behavior of CREATE INDEX CONCURRENTLY. See http://www.postgresql.org/docs/9.2/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY regards, tom lane