Re: pg15b2: large objects lost on upgrade

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg15b2: large objects lost on upgrade
Date: 2022-07-02 12:34:04
Message-ID: CA+TgmobwWGO98mWB1X2xpo25gatKsjpENtnYaUFcvVs7raRQPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 1, 2022 at 7:14 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> I noticed this during beta1, but dismissed the issue when it wasn't easily
> reproducible. Now, I saw the same problem while upgrading from beta1 to beta2,
> so couldn't dismiss it. It turns out that LOs are lost if VACUUM FULL was run.

Yikes. That's really bad, and I have no idea what might be causing it,
either. I'll plan to investigate this on Tuesday unless someone gets
to it before then.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-07-02 12:45:50 Re: replacing role-level NOINHERIT with a grant-level option
Previous Message Robert Haas 2022-07-02 12:27:55 Re: making relfilenodes 56 bits