| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication vs. float timestamps is a disaster |
| Date: | 2017-02-22 15:21:18 |
| Message-ID: | 8ac3b446-00e0-2813-e67a-0498fac0f9b0@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/22/17 9:12 AM, Andres Freund wrote:
>> That would allow an in-place upgrade of
>> a really large cluster. A user would still need to modify their code to use
>> the new type.
>>
>> Put another way: add ability for pg_upgrade to change the type of a field.
>> There might be other uses for that as well.
> Type oids are unfortunately embedded into composite and array type data
> - we can do such changes for columns themselves, but it doesn't work if
> there's any array/composite members containing the to-be-changed type
> that are used as columns.
Only in the catalog though, not the datums, right? I would think you
could just change the oid in the catalog the same as you would for a
table column.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-02-22 15:27:00 | Re: Replication vs. float timestamps is a disaster |
| Previous Message | Corey Huinker | 2017-02-22 15:20:33 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |