| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Chris Travers *EXTERN*" <chris(dot)travers(at)gmail(dot)com>, "Postgres General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Question about upgrading extensions |
| Date: | 2012-09-24 09:54:26 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C20874B8AA@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Chris Travers wrote:
> If one releases an extension with say a version number of 0.1 and then
releases one with important
> changes at 0.2, how is the best way to manage these changes? I
couldn't find anything in the docs to
> discuss this issue. Am I missing something?
>
> Specifically for pg_message_queue, for 0.2 I would like to change the
type of a field from text
> (constrained to 'text', 'xml' or 'bytea) to regtype. Not sure where
to put the DDL for an upgrade.
Into pg_message_queue--0.1--0.2.sql.
See
http://www.postgresql.org/docs/current/static/extend-extensions.html#AEN
54163
The command to upgrade an extension is ALTER EXTENSION UPDATE.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2012-09-24 10:06:00 | Python mapping with new 9.2 data types |
| Previous Message | Jasen Betts | 2012-09-24 09:48:36 | Re: Upgrade from 8.4.13 to 9.2.0.1 successful but it still displays 8.4.13 if SELECT version(); |