Request a Demo
Home   >   mailing lists

Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade - Mailing list pgsql-bugs

From Jeff Davis
Subject Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Date
Msg-id 614d31c9bef9152f90a60bb968f7e855e6164e9c.camel@j-davis.com
Whole thread Raw
In response to BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
List pgsql-bugs
Tree view 
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

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
Next
From: Tom Lane
Date:
Subject: Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction