From: | "Sander Steffann" <s(dot)steffann(at)computel(dot)nl> |
---|---|
To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade (was: 8.2 features status) |
Date: | 2006-08-07 17:30:58 |
Message-ID: | 001c01c6ba47$3f6de990$64c8a8c0@balefirehome |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
>> [ concerning handling a change in a single datatype's representation ]
>
>> 1. Under old system, munge the system catalog to add code for new inet
>> type with new OID. Probably needs a shared lib (if you could create
>> type input/output function with pl/pgsql it would help here).
>> 2. Execute ALTER COLUMN TYPE USING to switch to the new type.
>> 3. Shutdown old server
>> 4. Complete catalog changes
>> 5. Startup new version
>
> Probably easier and more flexible just to include both versions of the
> datatype in the new release, and tell people they'd better ALTER COLUMN
> TYPE sometime before updating to release N+2.
Sounds very nice to have for me! Add an easy way to see which columns are
still in the old format, and upgrading will be so much easier.
- Sander
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2006-08-07 17:32:18 | Re: "Constraint exclusion" is not general enough |
Previous Message | Joshua Reich | 2006-08-07 17:12:43 | Re: AOL Research open-research |