From: Jeff Davis <pgsql@j-davis.com>
To: yuri@yrz.am
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Date: Thu, 09 Oct 2025 09:56:24 -0700
Message-ID: <614d31c9bef9152f90a60bb968f7e855e6164e9c.camel@j-davis.com> (raw)
In-Reply-To: <19078-dfd62f840a2c0766@postgresql.org>
References: <19078-dfd62f840a2c0766@postgresql.org>
On Thu, 2025-10-09 at 08:35 +0000, PG Bug reporting form wrote:
> - Disabled enable_hashagg for some queries (just now)
Hi,
How sure are you that the crashes are happening without HashAgg? I made
some changes in that area in v18, and a lot of the evidence points in
that direction. Please let me know if you are able to confirm that the
simpler (non-hashagg) plan you showed is actually crashing.
Regards,
Jeff Davis
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: pgsql-bugs@postgresql.org
Cc: pgsql@j-davis.com, yuri@yrz.am, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
In-Reply-To: <614d31c9bef9152f90a60bb968f7e855e6164e9c.camel@j-davis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox