Обсуждение: Re: Extension relocation vs. schema qualification

"Verona, Luiz" <luverona@amazon.com> writes:
> I am writing to resurrect this 3-year-old thread. Attached is a patch to address earthdistance related failures
duringpg_restore. 
> The proposed patch will:
>  - Create a new version of earthdistance (1.2) and make this new version default
>  - Change earthdistance relocatable from true to false

That part seems like kind of a nonstarter.  People may already rely on it
being relocatable.  Also, if cube is still relocatable, it could still
get broken post-installation.

I spent some time awhile ago on fixing this via new-style SQL functions
[1].  That didn't get finished for reasons explained in the thread,
but I think that's probably a more productive direction to go in.

            regards, tom lane

[1] https://www.postgresql.org/message-id/flat/3395418.1618352794%40sss.pgh.pa.us

On Tue, Oct 5, 2021 at 8:26 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I spent some time awhile ago on fixing this via new-style SQL functions
> [1].  That didn't get finished for reasons explained in the thread,
> but I think that's probably a more productive direction to go in.

Hmm, if that'll solve the problem, +1 from me. I'm not a big fan of
giving up on the ability to relocate extensions. I know it's a pain to
support and I'm not sure that we have all the ideas we need to make it
work cleanly, but I don't feel like it should be intrinsically
impossible to get working, and I think users want it.

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