On 10.09.25 09:48, Pierrick wrote:
On 09/09/2025 16:18, Matheus Alcantara wrote:
On Tue Sep 9, 2025 at 4:53 AM -03, Pierrick wrote:
On 08/09/2025 17:35, Tom Lane wrote:
"David G. Johnston" writes:
On Monday, September 8, 2025, Matheus Alcantara
wrote:
On this step it will search the .control
"David G. Johnston" writes:
> On Monday, September 8, 2025, Matheus Alcantara
> wrote:
>> On this step it will search the .control
>> file on paths at extension_control_path in order and it will use the
>> first one that it finds and based on the .control file found it will
>> install the extensi
On 11/09/2025 16:11, Peter Eisentraut wrote:
Here is a patch for that. Please test it against your setup.
Thanks a lot. Here is a test, and IMHO, it looks good.
-- version 1 of monextension is in /tmp/extensions/share/extension
postgres=# show extension_control_path ;
extensi
On Monday, September 8, 2025, Matheus Alcantara
wrote:
> On Fri Sep 5, 2025 at 11:22 AM -03, Pierrick wrote:
> > If the same extension is in two different paths mentioned in
> > extension_control_path,
> > it is impossible to install the version of the last one.
> >
> > postgres=# show extension_
On Mon, Sep 8, 2025 at 12:23 PM David G. Johnston
wrote:
> Also seems like the extension location should be part of the output too.
>
I've posted a patch for this at [1]
[1] https://www.postgresql.org/message-id/DCTSKQAVOXIG.3A05JM1YORARK%40gmail.com
--
Matheus Alcantara
On 11.09.25 20:03, Pierrick wrote:
On 11/09/2025 16:11, Peter Eisentraut wrote:
Here is a patch for that. Please test it against your setup.
Thanks a lot. Here is a test, and IMHO, it looks good.
committed
On 11/09/2025 20:03, Pierrick wrote:
-- make a mistake in first folder
postgres=# alter system set extension_control_path =
'$system:/tmp/extension_old/share:/tmp/extensions/share';
ALTER SYSTEM
postgres=# select pg_reload_conf();
pg_reload_conf
t
(1 ligne)
-- still versio
On Mon, Sep 08, 2025 at 11:35:42AM -0400, Tom Lane wrote:
> Between this and previously-identified problems (commits 81eaaa2c4,
> f777d7738), it seems clear that extension_control_path (which is a new
> thing in v18) was very poorly thought out. I wonder if it's too late
> to revert it so that we
On 09/09/2025 16:18, Matheus Alcantara wrote:
On Tue Sep 9, 2025 at 4:53 AM -03, Pierrick wrote:
On 08/09/2025 17:35, Tom Lane wrote:
"David G. Johnston" writes:
On Monday, September 8, 2025, Matheus Alcantara
wrote:
On this step it will search the .control
file on paths at extension_control
On Tue Sep 9, 2025 at 4:53 AM -03, Pierrick wrote:
>
> On 08/09/2025 17:35, Tom Lane wrote:
>> "David G. Johnston" writes:
>>> On Monday, September 8, 2025, Matheus Alcantara
>>> wrote:
On this step it will search the .control
file on paths at extension_control_path in order and it will
On 08/09/2025 17:35, Tom Lane wrote:
"David G. Johnston" writes:
On Monday, September 8, 2025, Matheus Alcantara
wrote:
On this step it will search the .control
file on paths at extension_control_path in order and it will use the
first one that it finds and based on the .control file found
On Fri Sep 5, 2025 at 11:22 AM -03, Pierrick wrote:
> If the same extension is in two different paths mentioned in
> extension_control_path,
> it is impossible to install the version of the last one.
>
> postgres=# show extension_control_path ;
> extension_control_path
12 matches
Mail list logo
