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

From David Rowley
Subject Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Date
Msg-id CAApHDvo0T2BeC7o81sTKiZHr9f__KLu-DVRgcg=d-J9zpsb7UA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
List pgsql-bugs
On Sat, 18 Oct 2025 at 10:25, David Rowley <dgrowleyml@gmail.com> wrote:
> If this fails then maybe we're using the wrong iterator somewhere in
> nodeAgg.c. I can't see any other way for the iterator's 'end' field to
> be bigger than the table's size.

I started looking for places that this could happen and quickly found
the following code:

/*
* Switch to next grouping set, reinitialize, and restart the
* loop.
*/
select_current_set(aggstate, nextset, true);

perhash = &aggstate->perhash[aggstate->current_set];

ResetTupleHashIterator(hashtable, &perhash->hashiter);

The hash table and the iterator for each set are meant to be in the
same AggStatePerHash, but the above code moves to the next set,
changes the "perhash" then resets the next iterator using the previous
hash table.

I think that line needs to be:

ResetTupleHashIterator(perhash->hashtable, &perhash->hashiter);

David



pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Next
From: Yuri Zamyatin
Date:
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade