Re: #XX000: ERROR: tuple concurrently updated

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Dominique Devienne <ddevienne(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: #XX000: ERROR: tuple concurrently updated
Date: 2025-02-20 16:07:02
Message-ID: CAKAnmmLE-PhxTvB-fEOc3X=MhbH2R-HA9yRp0xnNO4coGRB0Ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Since you are willing to break the all one transaction rule, and if the
restores were created via pg_dump, you could use the --section argument to
split things up, run the "pre-data" sections serially, and the rest ("data"
and "post-data") concurrently.

--
Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-02-20 16:08:33 Re: v18 virtual columns
Previous Message Tom Lane 2025-02-20 16:05:50 Re: DROP ROLE as SUPERUSER