Re: BUG #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and hash_bytes (HashAgg executor)

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: kspark(at)nepes(dot)co(dot)kr, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and hash_bytes (HashAgg executor)
Date: 2026-06-05 14:10:01
Message-ID: aiLYudSt6KICP3lk@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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: kspark(at)nepes(dot)co(dot)kr
> 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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrei Lepikhov 2026-06-05 14:27:00 Hashed SAOP on composite type with non-hashable column errors at runtime
Previous Message Marko Grujic 2026-06-05 13:11:25 Re: BUG #19507: Auto-named partition table constraint conflicts