| From: | Hüseyin Demir <huseyin(dot)d3r(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laur(at)aon(dot)at> |
| 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-10 17:37:26 |
| Message-ID: | CAB5wL7aTaOyijT3qJF9jAQNrv1K74sQkEyu+zkb54rYDc_NBdg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> > > 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
>
> Thanks for the pg_upgrade test.
>
> Appreciated.
Rebased v6 on current master.
| Attachment | Content-Type | Size |
|---|---|---|
| v7-0001-pg_dump-skip-dangling-initprivs.patch | application/octet-stream | 9.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2026-07-10 23:23:21 | Re: BUG #19549: Physical replication slot xmin value stuck |
| Previous Message | Hüseyin Demir | 2026-07-10 07:00:35 | Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table |