public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Ana Almeida <[email protected]>
Cc: Tomas Vondra <[email protected]>
Cc: Jim Jones <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Nuno Azevedo <[email protected]>
Subject: Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
Date: Fri, 27 Mar 2026 08:44:40 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <VI0PR07MB10718C01F5A9FEBA311BFD1ED974CA@VI0PR07MB10718.eurprd07.prod.outlook.com>
References: <VI0PR07MB10718A4DC292E068C51404AB2974EA@VI0PR07MB10718.eurprd07.prod.outlook.com>
<[email protected]>
<VI0PR07MB10718EF78ABE3997751F55E5D974EA@VI0PR07MB10718.eurprd07.prod.outlook.com>
<[email protected]>
<VI0PR07MB10718C01F5A9FEBA311BFD1ED974CA@VI0PR07MB10718.eurprd07.prod.outlook.com>
On Fri, Mar 20, 2026 at 12:26:36PM +0000, Ana Almeida wrote:
> We executed DELETE, VACUUM, and REINDEX commands multiple
> times. During one of the executions, the REINDEX operation failed
> with the error: "could not open file". After this, we dropped and
> recreated the database and repeated the tests. In one of the
> executions, the same REINDEX command resulted in segmentation fault,
> which caused the database to crash. When the REINDEX command failed,
> it left behind temporary index copies with the _ccnew suffix. We
> manually dropped these indexes and re-ran the REINDEX command, which
> then completed successfully.
I am afraid that it is one of these cases where having a
self-contained workload to be able to reproduce the issue, even if the
issue can be hit at a very low rate, would be super useful before we
could categorize that as a backend core issue. I could buy that there
is an in-core problem, but it's hard to justify the time investment
based on an assumption that we may have a problem.
FWIW, I have not seen such problematic error patterns lately, so it's
hard to say. I'll double-check around me and see if there is some data
to fish. Perhaps there is something matching with a portion of your
problematic patterns, or that has a similar smell.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox