public inbox for [email protected]  

help / color / mirror / Atom feed

From: John Naylor <[email protected]>
To: [email protected]
To: [email protected]
Subject: Re: BUG #19530: Crash (SIGSEGV/SIGBUS) in parallel B-tree index vacuum during plain VACUUM
Date: Mon, 22 Jun 2026 16:51:23 +0700
Message-ID: <CANWCAZaQ8sxPy2w0zWExnJXsK9t0y4AAxhENz3mhaO1Z2wdFoA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Mon, Jun 22, 2026 at 3:19 PM PG Bug reporting form
<[email protected]> wrote:
> PostgreSQL 17.7 intermittently crashes a parallel maintenance worker during
> routine VACUUM, taking the server through automatic crash recovery each
>   time.

>   What the crashing process was doing:
>   The crashing process is a parallel maintenance worker. A preserved core
> dump shows the process title "parallel worker for PID <leader>", with memory
>   contexts "BTree Vacuum State" and "AutoVacuum Data" present and no

This doesn't really give us any actionable info. Are you able to get a
backtrace from the core dump?

(Autovacuum in v17 cannot use parallel workers, so I'm not sure where
that came from)

>   Possibly related:
>   This appears to reach the same btbulkdelete / btvacuumscan code as the
> report "Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE
>   CONCURRENTLY"
> (https://www.postgresql.org/message-id/[email protected]...),
> but reached
>   via the plain-VACUUM index-vacuum path rather than validate_index /
> ReindexRelationConcurrently. That suggests the fault is in the (parallel)
> B-tree
>   index-vacuum code, reachable from both paths.

That operation was writing TIDs to a file, which is not what vacuum
does, and it's not clear from that thread whether there's a bug in the
first place.

--
John Naylor
Amazon Web Services

view thread (2+ messages)

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]
  Subject: Re: BUG #19530: Crash (SIGSEGV/SIGBUS) in parallel B-tree index vacuum during plain VACUUM
  In-Reply-To: <CANWCAZaQ8sxPy2w0zWExnJXsK9t0y4AAxhENz3mhaO1Z2wdFoA@mail.gmail.com>

* 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