Re: pg15b2: large objects lost on upgrade

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Shruthi Gowda <gowdashru(at)gmail(dot)com>
Subject: Re: pg15b2: large objects lost on upgrade
Date: 2022-07-11 01:31:06
Message-ID: Yst9Wc/
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Jul 08, 2022 at 10:44:07AM -0400, Robert Haas wrote:
> Thanks for checking over the reasoning, and the kind words in general.

Thanks for fixing the main issue.

> I just committed Justin's fix for the bug, without fixing the fact
> that the new cluster's original pg_largeobject files will be left
> orphaned afterward. That's a relatively minor problem by comparison,
> and it seemed best to me not to wait too long to get the main issue
> addressed.

Hmm. That would mean that the more LOs a cluster has, the more bloat
there will be in the new cluster once the upgrade is done. That could
be quite a few gigs worth of data laying around depending on the data
inserted in the source cluster, and we don't have a way to know which
files to remove post-upgrade, do we?

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2022-07-11 01:57:07 Re: Extending outfuncs support to utility statements
Previous Message Michael Paquier 2022-07-11 01:22:32 Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~