Date: Fri, 5 Jun 2026 10:10:01 -0400
From: Bruce Momjian <bruce@momjian.us>
To: kspark@nepes.co.kr, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19512: PG 17.10: SIGSEGV in build_minmax_path (planner) and
 hash_bytes (HashAgg executor)
Message-ID: <aiLYudSt6KICP3lk@momjian.us>
References: <19512-507749042aab33c7@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19512-507749042aab33c7@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/aiLYudSt6KICP3lk%40momjian.us>
Precedence: bulk

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@nepes.co.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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

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