From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |
Date: | 2019-05-04 13:06:37 |
Message-ID: | 20190504130637.GA5975@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 02, 2019 at 07:18:19PM -0400, Tom Lane wrote:
> I did manually verify that all branches get through "reindex table
> pg_class" and "reindex index pg_class_oid_index" under
> CLOBBER_CACHE_ALWAYS, as well as a normal-mode check-world. But CCA
> world runs seem like a good idea.
(catching up a bit..)
sidewinder is still pissed of as of HEAD, pointing visibly to f912d7d
as the root cause:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2019-05-03%2021%3A45%3A00
REINDEX TABLE pg_class; -- mapped, non-shared, critical
+ERROR: deadlock detected
+DETAIL: Process 28266 waits for ShareLock on transaction 2988;
blocked by process 20650.
+Process 20650 waits for RowExclusiveLock on relation 1259 of
database 16387; blocked by process 28266.
+HINT: See server log for query details.
I don't think that's sane just before the upcoming release..
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2019-05-04 13:16:57 | make maintainer-clean and config.cache |
Previous Message | Michael Paquier | 2019-05-04 12:59:20 | Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right? |