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 CAApHDvqS_SwUEKbgfNezy42QHsd8BJEgBNLFZ-OAtJogXBfT1Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade  (Yuri Zamyatin <yuri@yrz.am>)
Responses Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
Next
From: Nathan Bossart
Date:
Subject: Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.