Re: v12.0: segfault in reindex CONCURRENTLY - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: v12.0: segfault in reindex CONCURRENTLY
Date
Msg-id 20191013235716.GA25169@paquier.xyz
Whole thread Raw
In response to Re: v12.0: segfault in reindex CONCURRENTLY  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: v12.0: segfault in reindex CONCURRENTLY
List pgsql-hackers
On Sun, Oct 13, 2019 at 04:18:34PM -0300, Alvaro Herrera wrote:
> True.  And we can copy the resulting comment to the other spot.
>
> (FWIW I expect the crash is possible not just in reindex but also in
> CREATE INDEX CONCURRENTLY.)

I need to think about that, but shouldn't we have a way to reproduce
that case rather reliably with an isolation test?  The patch looks to
good to me, these are also the two places I spotted yesterday after a
quick lookup.  The only other caller is isTempNamespaceInUse() which
does its thing correctly.
--
Michael

Attachment

pgsql-hackers by date:

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