From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extension Packaging |
Date: | 2011-04-28 13:21:16 |
Message-ID: | BANLkTi=-qmdTji08A+pXJE8SVJeGBMeWTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 28, 2011 at 4:07 PM, Daniele Varrazzo
<daniele(dot)varrazzo(at)gmail(dot)com> wrote:
> On Wed, Apr 27, 2011 at 1:48 PM, Dimitri Fontaine
> <dimitri(at)2ndquadrant(dot)fr> wrote:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> If you didn't change the install script then it's not necessary to
>>> execute ALTER EXTENSION ... UPGRADE. You seem to be assuming that the
>>> pg_extensions catalog has to reflect the bug fix level of an extension,
>>> but that is *not* the intention. If it did reflect that, you'd need
>>> N times as many upgrade scripts, most of them identical, to deal with
>>> updating from different bug fix levels of the prior version.
>>
>> +1 — but this discussion shows we're not exactly finished here.
>
> Probably what is needed is only a clarification that the version
> number is only about schema object, not revision, patch level, release
> status or whatever else semantically meaningful. I've attached a patch
> for the docs about the point.
How about each .so containing a version callback?
Thus you can show what is the version of underlying implementation
without needing to mess with catalogs just to keep track of patchlevel
of C code.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-28 13:25:33 | Re: VX_CONCURRENT flag on vxfs( 5.1 or later) for performance for postgresql? |
Previous Message | Daniele Varrazzo | 2011-04-28 13:07:32 | Re: Extension Packaging |