Re: pg15b2: large objects lost on upgrade - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg15b2: large objects lost on upgrade
Date
Msg-id CA+Tgmoavavffv2GTtZ-1=QUxZh020xfUUAOS6mXd9u_zFQ=9Qw@mail.gmail.com
Whole thread Raw
In response to Re: pg15b2: large objects lost on upgrade  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: pg15b2: large objects lost on upgrade
List pgsql-hackers
On Wed, Jul 6, 2022 at 7:56 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
> I'm looking into it, but it'd help to hear suggestions about where to put it.
> My current ideas aren't very good.

In main() there is a comment that begins "Most failures happen in
create_new_objects(), which has just completed at this point." I am
thinking you might want to insert a new function call just before that
comment, like remove_orphaned_files() or tidy_up_new_cluster().

Another option could be to do something at the beginning of
transfer_all_new_tablespaces().

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



pgsql-hackers by date:

Previous
From: Svetlana Derevyanko
Date:
Subject: Re[2]: [PATCH] Optional OR REPLACE in CREATE OPERATOR statement
Next
From: Matthias van de Meent
Date:
Subject: Re: doc: Fix description of how the default user name is chosen