| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "pgsql-hackers\(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Subject: | Re: Extension Packaging |
| Date: | 2011-05-12 07:29:26 |
| Message-ID: | m2d3jofkbt.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)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.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2011-05-12 07:42:22 | Re: Tables cannot have INSTEAD OF triggers |
| Previous Message | Heikki Linnakangas | 2011-05-12 07:04:31 | Re: |