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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Yuri Zamyatin <yuri(at)yrz(dot)am>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Date: 2025-10-14 21:44:19
Message-ID: CAApHDvqS_SwUEKbgfNezy42QHsd8BJEgBNLFZ-OAtJogXBfT1Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 15 Oct 2025 at 04:51, Yuri Zamyatin <yuri(at)yrz(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nathan Bossart 2025-10-14 22:03:12 Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
Previous Message Tom Lane 2025-10-14 19:50:15 Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.