Re: Extensions, patch v16 - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Extensions, patch v16
Date
Msg-id 04229729-4C01-4CEE-B95D-21463D547FEF@kineticode.com
Whole thread Raw
In response to Re: Extensions, patch v16  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Dec 10, 2010, at 10:20 AM, Tom Lane wrote:

> True.  Consider a situation like an RPM upgrade: it's going to drop in a
> new .so version, *and nothing else*.  It's pure fantasy to imagine that
> the RPM script is going to find all your databases and execute some SQL
> commands against them.  Since a large number of bug-fix cases do require
> only a .so update, not being able to track the .so version seems like
> it's missing most of the argument for having version tracking at all.

Sometimes there will be changes to the SQL, too. How does that work with CREATE EXTENSION? Do I install the upgrade,
thenrun CREATE EXTENSION to get the latest SQL script to run? But then all the objects already exist… 

Best,

David

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Extensions, patch v16
Next
From: Dimitri Fontaine
Date:
Subject: Re: Extensions, patch v16