v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock on object14185/39327/0 is already held - Mailing list pgsql-hackers

From Justin Pryzby
Subject v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock on object14185/39327/0 is already held
Date
Msg-id 20191013025145.GC4475@telsasoft.com
Whole thread Raw
Responses Re: v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock onobject 14185/39327/0 is already held
Re: v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock onobject 14185/39327/0 is already held
List pgsql-hackers
I ran into this while trying to trigger the previously-reported segfault. 

CREATE TABLE t(i) AS SELECT * FROM generate_series(1,9);
CREATE INDEX ON t(i);

[pryzbyj@database ~]$ for i in `seq 1 9`; do PGOPTIONS='-cstatement_timeout=9' psql postgres --host /tmp --port 5678 -c
"REINDEXINDEX CONCURRENTLY t_i_idx" ; done
 
ERROR:  canceling statement due to statement timeout
ERROR:  lock ShareUpdateExclusiveLock on object 14185/47287/0 is already held
[...]

Variations on this seem to leave the locks table (?) or something else in a
Real Bad state, such that I cannot truncate the table or drop it; or at least
commands are unreasonably delayed for minutes, on this otherwise-empty test
cluster.

Justin



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: CREATE TEXT SEARCH DICTIONARY segfaulting on 9.6+
Next
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions