Re: pg_upgrade failing for 200+ million Large Objects - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: pg_upgrade failing for 200+ million Large Objects
Date
Msg-id d93ba90d8bb7e0666c4d23e2478485189c14965a.camel@cybertec.at
Whole thread Raw
In response to Re: pg_upgrade failing for 200+ million Large Objects  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 2024-03-16 at 18:46 -0400, Tom Lane wrote:
> > Without the patch:
> > Runtime: 74.5 minutes
>
> > With the patch:
> > Runtime: 70 minutes
>
> Hm, I'd have hoped for a bit more runtime improvement.

I did a second run with the patch, and that finished in 66 minutes,
so there is some jitter there.

I think the reduced memory footprint and the reduced transaction ID
consumption alone make this patch worthwhile.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: BitmapHeapScan streaming read user and prelim refactoring
Next
From: Noah Misch
Date:
Subject: Re: Autogenerate some wait events code and documentation