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

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>
To: Yuri Zamyatin <yuri@yrz.am>
Cc: Jeff Davis <pgsql@j-davis.com>, pgsql-bugs@lists.postgresql.org
Date: 2025-10-14T21:44:19Z
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

On Wed, 15 Oct 2025 at 04:51, Yuri Zamyatin <yuri@yrz.am> wrote:
> To cause the segfault, these queries were launched simultaneously.
>
> > -- in 2 parallel infinite loops
> > with ids as (select (118998526-random()*100000)::int id from generate_series(1,10000))
> > update tcv_scene_datas set id=id where cv_scene_id in(select id from ids);
> > with ids as (select (118998526-random()*100000)::int id from generate_series(1,10000))
> > update tcv_scenes set id=id where id in(select id from ids);

Are you able to mock this up using the schema and some test data then
share the script to populate the database?

David