Re: Extensions, patch v16

David Wheeler <david@kineticode.com>

From: "David E. Wheeler" <david@kineticode.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Robert Haas <robertmhaas@gmail.com>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2010-12-10T18:21:56Z

Lists: 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, then run CREATE EXTENSION to get the latest SQL script to run? But then all the objects already exist…

Best,

David