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

From Alvaro Herrera
Subject Re: v12.0: segfault in reindex CONCURRENTLY
Date
Msg-id 20191013181021.GA10785@alvherre.pgsql
Whole thread Raw
In response to Re: v12.0: segfault in reindex CONCURRENTLY  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: v12.0: segfault in reindex CONCURRENTLY
List pgsql-hackers
On 2019-Oct-13, Justin Pryzby wrote:

> Looks like it's a race condition and dereferencing *holder=NULL.  The first
> crash was probably the same bug, due to report query running during "reindex
> CONCURRENTLY", and probably finished at nearly the same time as another locker.

Ooh, right, makes sense.  There's another spot with the same mistake ...
this patch should fix it.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: v12.0: ERROR: could not find pathkey item to sort
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Deadlock in XLogInsert at AIX