On Thu, May 12, 2011 at 3:29 AM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>>> Okay, how we add a "revision" key to the control file and extrevision to
>>> the pg_extension catalog. Its type can be "TEXT" and is optional for use
>>> by extensions.
>>
>> How would pg_extension.extrevision be kept up to date? AFAICS, the
>> whole point is that you might swap out the shared libraries without
>> doing anything at the SQL level.
>
> Well, ALTER EXTENSION UPDATE could be taught to check for control file
> changes only when there's no upgrade script. I think it already did
> that for some fields, like require and comment, but it's no longer the
> case.
>
> Still, I would think that it should be possible to update some metadata
> of the extension without running an SQL upgrade script.
The point is that something like RPM is not going to run *any* SQL
command. It's just going to replace the files in the filesystem. If
the view can pull that info from some file on the fly, then it can be
pretty much guaranteed to be up-to-date and accurate. Anything else
seems hit or miss.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company