From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Verona, Luiz" <luverona(at)amazon(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Extension relocation vs. schema qualification |
Date: | 2021-10-06 14:44:44 |
Message-ID: | CA+TgmoY8FM7Vq-mJuS57eDbQuCiSZHmwvpnRD6R6Rcvcjog6YQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Tue, Oct 5, 2021 at 8:26 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Borisov | 2021-10-06 15:14:21 | Re: BUG #17212: pg_amcheck fails on checking temporary relations |
Previous Message | Tom Lane | 2021-10-06 14:16:31 | Re: BUG #17216: No Password Provided Error - uncaught exception |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2021-10-06 14:53:29 | Re: Compressing temporary files |
Previous Message | Robert Haas | 2021-10-06 14:41:43 | Re: Triage on old commitfest entries |