public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: [email protected]
To: [email protected]
Subject: Re: BUG #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and hash_bytes (HashAgg executor)
Date: Fri, 5 Jun 2026 10:10:01 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Fri, Jun  5, 2026 at 01:49:46AM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      19512
> Logged by:          Kay
> Email address:      [email protected]
> PostgreSQL version: 17.10
> Operating system:   Ubuntu 24.04 LTS, kernel 6.8.0-110-generic, x86_64
> Description:        
> 
> PostgreSQL 17.10 (pgdg, Ubuntu 24.04) crashes with SIGSEGV in two
> unrelated code paths when planning / executing aggregate queries
> against a busy TimescaleDB hypertable. Both stacks are entirely
> inside core PG (the TimescaleDB planner hook is on the stack but
> the crash address is below it in PG core, not inside the extension's
> .so). Five cluster-wide cascade restarts in 2 hours today, plus 5
> distinct events over the preceding 72 hours.

The only thing I can add is that it is possible for an extension like
TimescaleDB to cause a crash in the Postgres sections of the code.

-- 
  Bruce Momjian  <[email protected]>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

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 #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and hash_bytes (HashAgg executor)
  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