Re: Upgrading Extension, version numbers (was: Extensions, patch v16) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Upgrading Extension, version numbers (was: Extensions, patch v16)
Date
Msg-id 23428.1294083745@sss.pgh.pa.us
Whole thread Raw
In response to Re: Upgrading Extension, version numbers (was: Extensions, patch v16)  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Upgrading Extension, version numbers (was: Extensions, patch v16)  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> On Dec 29, 2010, at 2:01 PM, Dimitri Fontaine wrote:
>> At the time you tell PostgreSQL about the new extension, the shared
>> object file has been in place for some time already, and the upgrade SQL
>> script has not been ran yet.

> That sounds dangerous.

It is, but I don't see any alternative.  As Dimitri said, the .so will
typically be installed by a packaging system, so we don't have any
opportunity to run SQL code beforehand.  In any case ...

> The new .so should not be installed until the upgrade is been run.

... that flat out doesn't work.  If the upgrade script tries to add
functions that didn't exist in the old .so, it'll fail.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: back branches vs. VS 2008
Next
From: "David E. Wheeler"
Date:
Subject: Re: Upgrading Extension, version numbers (was: Extensions, patch v16)