Horton

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

amit <amitlangote09@gmail.com>

View thread
From: Amit Langote <amitlangote09@gmail.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Yuri Zamyatin <yuri@yrz.am>, Jeff Davis <pgsql@j-davis.com>, pgsql-bugs@lists.postgresql.org
Date: 2025-10-16T03:29:22Z
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 →

  1. Fix reset of incorrect hash iterator in GROUPING SETS queries

  2. Fix EPQ crash from missing partition directory in EState

Attachments

On Thu, Oct 16, 2025 at 7:51 AM David Rowley <dgrowleyml@gmail.com> wrote:
> On Thu, 16 Oct 2025 at 11:45, David Rowley <dgrowleyml@gmail.com> wrote:
> >
> > On Thu, 16 Oct 2025 at 03:21, Yuri Zamyatin <yuri@yrz.am> wrote:
> > > In 1-2 minutes, 5 processes died with segfault.

Thanks Yuri for the report and the test case.

> >
> > Perfect. Thank you.
> >
> > It seems to be some more forgotten EPQ stuff from d47cbf474.  Amit got
> > some of these in 8741e48e5, but evidently the test case didn't do
> > pruning during execution, (only init plan pruning) so the partition
> > directory wasn't needed.
>
> I forgot to mention, this isn't the same thing as the
> tts_minimal_store_tuple() issue you first reported, so if there is a
> problem there, this one has nothing to do with it.

Thanks again, David.

I've attached an updated patch with a test case.

-- 
Thanks, Amit Langote