Tom Lane writes:
> I'm just wondering whether applying that theory is leading to the
> right choices here. In particular, the default behavior if you didn't
> say "SCHEMA something" would be to automatically move the extension
> into whatever random schema happens to be the front of your search_p
On Feb 16, 2011, at 3:00 PM, Tom Lane wrote:
> According to our prior discussions of C.O.R. commands, the general
> principle that such a command ought to follow is that upon success,
> the object exists with exactly the properties implied by the command's
> arguments. So (1) if the extension isn
Dimitri Fontaine writes:
> Tom Lane writes:
>> Another thought is that it'd probably be useful for there to be a
>> "CREATE OR REPLACE EXTENSION" syntax, with the behavior of "install the
>> extension if it's not present, else make sure it's of the specified or
>> default version"; this behavior
Tom Lane writes:
> ERROR: version to install or update to must be different from old version
>
> On reflection it seems like this is overly paranoid, and it'd be more
> useful if the ALTER just reported a NOTICE along the lines of "version
> so-and-so is already installed". Any objections?
I se
On Feb 15, 2011, at 5:18 PM, Tom Lane wrote:
> Currently, ALTER EXTENSION UPDATE throws an error if there's nothing to
> do:
>
> regression=# create extension adminpack ;
> CREATE EXTENSION
> regression=# alter extension adminpack update;
> ERROR: version to install or update to must be differen
Currently, ALTER EXTENSION UPDATE throws an error if there's nothing to
do:
regression=# create extension adminpack ;
CREATE EXTENSION
regression=# alter extension adminpack update;
ERROR: version to install or update to must be different from old version
On reflection it seems like this is over
