Subject: Re: Replication vs. float timestamps is a disaster
To: Andres Freund <andres@anarazel.de>
References: 
 <CA+TgmoafyUzmg8T-rKEgmkX7F1iQLSrKBmqKa26EattXpMS-ng@mail.gmail.com>
 <1691.1487519369@sss.pgh.pa.us>
 <20170220070311.gscn7ppqbwlgdpjq@alap3.anarazel.de>
 <3bd3c551-8b23-45c8-27a2-97b5a922b130@2ndquadrant.com>
 <20170220110456.2jupmfhxlizykmmc@alap3.anarazel.de>
 <fece0003-6ede-ca8b-8f26-3c6fa899583d@BlueTreble.com>
 <20170222075345.mbzrmdaetdqfgitk@alap3.anarazel.de>
 <21041.1487771008@sss.pgh.pa.us>
 <20170222135634.gnlqu6by2xbpvwii@alap3.anarazel.de>
 <49985f09-7498-9a84-008b-638cbaebb044@BlueTreble.com>
 <20170222151230.zy7q7qmfah22lcxt@alap3.anarazel.de>
CC: Tom Lane <tgl@sss.pgh.pa.us>, Petr Jelinek <petr.jelinek@2ndquadrant.com>,
	Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org"
	<pgsql-hackers@postgresql.org>
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
Message-ID: <8ac3b446-00e0-2813-e67a-0498fac0f9b0@BlueTreble.com>
Date: Wed, 22 Feb 2017 09:21:18 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170222151230.zy7q7qmfah22lcxt@alap3.anarazel.de>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: None (protection.outlook.com: bluetreble.com does not designate
 permitted sender hosts)
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Feb 2017 15:21:25.8229 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1646
X-Pg-Spam-Score: -2.3 (--)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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)


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers