Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: yuri(at)yrz(dot)am, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Date: 2025-10-09 16:56:24
Message-ID: 614d31c9bef9152f90a60bb968f7e855e6164e9c.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-10-09 17:17:52 Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
Previous Message PG Bug reporting form 2025-10-09 15:44:15 BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction