Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table

From: Laurenz Albe <laur(at)aon(dot)at>
To: Hüseyin Demir <huseyin(dot)d3r(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
Date: 2026-07-02 21:09:54
Message-ID: ec8f6c8008cf88577b14489b68fef971f16960ab.camel@aon.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 2026-06-26 at 10:30 +0200, Laurenz Albe wrote:
> I'd say that your v6 patch is fine if the performance impact can be
> shown to be small.

To keep the ball rolling, I ran a pg_upgrade --link from a debug-enabled
build on a database with 20000 empty tables.

pg_upgrade took between 19 and 25 minutes, and I saw no noticeable effect
of the patch. So I guess this is good to go.

Yours,
Laurenz Albe

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2026-07-02 22:10:08 Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
Previous Message Peter Geoghegan 2026-07-02 18:32:31 Re: BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash