From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Add CREATE EXTENSION Support |
Date: | 2014-02-12 17:20:19 |
Message-ID: | 27035715-8D1E-4CED-981F-B35C5926B831@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Feb 12, 2014, at 2:21 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Much as PostgreSQL only changes catalogs and on disk format in major
> releases, pgAgent only changes its schema in X releases (in the X.Y.Z
> numbering scheme). My point is that there is no need to have upgrade
> scripts from 3.3.0 - 3.4.0 or even 3.3 - 3.4 because there will never
> be any such changes, and using that numbering is likely to confuse
> users because the existence of a 3.4.0 script implies that there also
> should be one for 3.4.1 or 3.5.0 in the future, when in actual fact,
> there will only be one needed for 4(.x.x).
>
> Therefore, I believe the correct option is actually to have
> "pgagent--unpackaged--3.sql" and later "pgagent--3--4.sql" for
> upgrades.
Yeah, but if the version is 3.4.0, and that's what's in pgagent.spec, then Postgres will never find the upgrade script if it’s not named "pgagent--unpackaged--3.4.0.sql". The name in the file must be the same as in the spec file.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2014-02-12 21:58:49 | pgAdmin III commit: Give more options with the plain format |
Previous Message | Dave Page | 2014-02-12 12:01:29 | Re: Ways to improve PgAdmin III SQL context help |