Message-ID: <f80ee747-1efa-453b-822c-131ad00b62cf@mailbox.org>
Date: Thu, 12 Dec 2024 22:19:11 -0800
MIME-Version: 1.0
Subject: Re: Errors when restoring backup created by pg_dumpall
To: Adrian Klaver <adrian.klaver@aklaver.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
 "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
References: <6a6439f1-8039-44e2-8fb9-59028f7f2014@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>
 <e287682a-86ff-4201-b6d7-d574d0eead54@mailbox.org>
 <16a6330b-9e6c-4f09-974b-075a7facb4c5@aklaver.com>
 <dd5edafb-414d-42f5-9862-39da88d1df94@mailbox.org>
 <2b1143ef-2740-437a-a68d-664bb36beca8@aklaver.com>
Content-Language: en-US
From: PopeRigby <poperigby@mailbox.org>
In-Reply-To: <2b1143ef-2740-437a-a68d-664bb36beca8@aklaver.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/f80ee747-1efa-453b-822c-131ad00b62cf%40mailbox.org>
Precedence: bulk

On 12/10/24 21:22, Adrian Klaver wrote:
> On 12/10/24 19:05, PopeRigby wrote:
>> On 12/9/24 16:31, Adrian Klaver wrote:
>>> On 12/9/24 15:30, PopeRigby wrote:
>>>> 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].
>>>>>
>>>>> 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 unclear.
>>>>>
>>>>>             regards, tom lane
>>>>>
>>>>> [1] 
>>>>> https://www.postgresql.org/message-id/flat/3395418.1618352794@sss.pgh.pa.us
>>>>
>>>> I compiled and installed PostgreSQL with the patch, and restarted 
>>>> it, so unless there are other steps I'm not sure what I could have 
>>>> done wrong.
>>>>
>>>
>>>
>>> What was the source of the patch?
>>>
>> This: 
>> https://www.postgresql.org/message-id/attachment/122092/0002-earthdistance-sql-functions.patch
>>
>
> If I am following correctly I believe you need this one:
>
> https://www.postgresql.org/message-id/attachment/166859/v2-0002-Use-new-style-SQL-function-in-earthdistance-exten.patch 
>
>
> It has the changes that include the schema qualifications. The one you 
> used does not have those modifications.
>
Beautiful. How can I follow this so I know when it gets upstream?