Re: Horribly slow pg_upgrade performance with many Large Objects

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Nitin Motiani <nitinmotiani(at)google(dot)com>, Hannu Krosing <hannuk(at)google(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Horribly slow pg_upgrade performance with many Large Objects
Date: 2025-07-18 16:05:04
Message-ID: aHpwsGXSicLArZSk@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Committed.

I'm cautiously optimistic that we can find some better gains for upgrades
from v16 and newer. That would involve dumping lo_create() commands for
all LOs with comments/seclabels, dumping the relevant pg_shdepend rows, and
then copying/linking the pg_largeobject_metadata files like we did prior to
v12.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-07-18 16:26:38 Re: Making type Datum be 8 bytes everywhere
Previous Message Jehan-Guillaume de Rorthais 2025-07-18 15:53:14 [(known) BUG] DELETE/UPDATE more than one row in partitioned foreign table