Only one version can be installed when using extension_control_path - Mailing list pgsql-hackers

From Pierrick
Subject Only one version can be installed when using extension_control_path
Date
Msg-id 8f5a0517-1cb8-4085-ae89-77e7454e27ba@dalibo.com
Whole thread Raw
List pgsql-hackers

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                            
-----------------------------------------------------------------------------
 $system:/extensions/meilleureextension/share:/extensions/monextension/share
(1 row)

postgres=# select * from pg_available_extensions where name like '%mon%';
     name     | default_version | installed_version |    comment    
--------------+-----------------+-------------------+---------------
 monextension | 2.0             |                   | Meilleure
 monextension | 1.0             |                   | Mon extension
(2 rows)
postgres=# create extension monextension version "1.0" ;
ERROR:  extension "monextension" has no installation script nor update path for version "1.0"
postgres=# create extension monextension ;
CREATE EXTENSION
postgres=# select * from pg_available_extensions where name like '%mon%';     name     | default_version | installed_version |    comment
--------------+-----------------+-------------------+--------------- monextension | 2.0             | 2.0               | Meilleure monextension | 1.0             | 2.0               | Mon extension


Don't you think that the command

create extension monextension version "1.0" ;

should be accepted by checking in all paths ?

Pierrick,



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Appetite for syntactic sugar to match result set columns to UDT fields?
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Differential Code Coverage report for Postgres