Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: yuri@yrz.am, pgsql-bugs@lists.postgresql.org
Date: 2025-10-09T16:56:24Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix reset of incorrect hash iterator in GROUPING SETS queries
- 0b6a02f0355c 18.1 landed
- 5c0a20003b43 19 (unreleased) landed
-
Fix EPQ crash from missing partition directory in EState
- 1296dcf18b1c 18.1 landed
- 905e932f0922 19 (unreleased) landed
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