Feedback-ID: i76984098:Fastmail
Message-ID: <acd132de-5014-4c20-9738-07a6c8a3f626@aklaver.com>
Date: Mon, 9 Dec 2024 16:07:53 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Errors when restoring backup created by pg_dumpall
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PopeRigby <poperigby@mailbox.org>,
 "David G. Johnston" <david.g.johnston@gmail.com>,
 "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
References: <6a6439f1-8039-44e2-8fb9-59028f7f2014@mailbox.org>
 <CAKFQuwaB5GuUNuyiUbS0ah-LYXepHLPnOHrP7g8RMz8ywOm3zQ@mail.gmail.com>
 <ff94f628-27af-4c3a-9590-cba38bb5d2d1@mailbox.org>
 <CAKFQuwYQUequkYVS8SLgC1L0TOdWNK=xVyxnPD9RPPwfvYRFSQ@mail.gmail.com>
 <41791b6d-aaf5-4fed-9cc3-e89bc49e8637@mailbox.org>
 <CAKFQuwbe4TSU_LxsrGxgcv4DfQq2x-UNoyKx-ABy36PhvbGCdg@mail.gmail.com>
 <1257068.1733025493@sss.pgh.pa.us>
 <06425038-e012-4bac-aec1-d9541436f893@mailbox.org>
 <92405f98-7f0c-4442-8252-697352daefc1@aklaver.com>
 <1470486.1733087658@sss.pgh.pa.us>
 <4ab662d8-57cc-471f-8a58-cfd71d1cea22@aklaver.com>
 <1475512.1733090108@sss.pgh.pa.us>
 <19d5f2c7-1252-4442-accb-8aa2cb289ad0@mailbox.org>
 <f84a6583-50cc-416b-9abd-2b5795aa74ac@aklaver.com>
 <aa9df674-0f08-458b-8f09-08cfb57b915c@mailbox.org>
 <CAKFQuwZf+1frb+82G2-2tD84GXEpuCG_WZaiAU46=L2PDa9gYw@mail.gmail.com>
 <9a7ca237-7696-40e3-9ae6-12bd98c1b86c@mailbox.org>
 <5dc9dd9e-a3c9-45a1-8497-7e304812eb! 8c@aklaver.com>
 <4147349.1733786606@sss.pgh.pa.us>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <4147349.1733786606@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/acd132de-5014-4c20-9738-07a6c8a3f626%40aklaver.com>
Precedence: bulk

On 12/9/24 15:23, Tom Lane wrote:
> Adrian Klaver <adrian.klaver@aklaver.com> writes:
>> You could file an issue here:
>> https://www.postgresql.org/account/login/?next=/account/submitbug/
>> Ask if the developers could use the mechanisms available here:
>> https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-RELOCATION
> 
> This wouldn't really move the needle, since (a) there is not some
> magic group of people that will become involved who aren't already
> and (b) the requested fix seems exactly the same as the work
> already in progress at [1].

I made the suggestion to the OP, my mistake. Somewhere I missed that 
work was being done on this.

> 
> What would help is to figure out why the proposed patch didn't
> seem to work for you.  I continue to suspect that you didn't
> really install the updated extension, but it's unclea

Are you referring to this?:

https://www.postgresql.org/message-id/3316564.aeNJFYEL58@aivenlaptop

> 
> 			regards, tom lane
> 
> [1] https://www.postgresql.org/message-id/flat/3395418.1618352794@sss.pgh.pa.us

-- 
Adrian Klaver
adrian.klaver@aklaver.com