Skip site navigation (1) Skip section navigation (2)

Re: Numeric 508 datatype

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Numeric 508 datatype
Date: 2005-11-18 11:11:09
Message-ID: 437DB6CD.20601@pse-consulting.de (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-patches
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> 
>>However, I don't think we can promise never to change the ondisk 
>>representation of data, nor the page layout. Sometimes an inplace 
>>upgrade just won't work, ISTM.
> 
> 
> We have talked about batching on-disk changes so that they'd only occur
> once every few release cycles.  But until we have a pg_upgrade, there is
> no reason to adopt such a policy.

IMHO such a policy is a _prerequisite_ for somebody to come up 
implementing pg_upgrade. Why spend time on pg_upgrade if there's no 
policy to support it?

Regards,
Andreas

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2005-11-18 11:32:07
Subject: Re: Numeric 508 datatype
Previous:From: Zeugswetter Andreas DCP SDDate: 2005-11-18 10:45:33
Subject: Re: Improving count(*)

pgsql-patches by date

Next:From: Aftab AlamDate: 2005-11-18 11:17:10
Subject: trigger
Previous:From: Mark KirkwoodDate: 2005-11-18 05:30:11
Subject: Re: TODO Item - Add system view to show free space map

pgsql-general by date

Next:From: Csaba NagyDate: 2005-11-18 11:13:00
Subject: How to debug a locked backend ?
Previous:From: Wolfgang KellerDate: 2005-11-18 10:00:51
Subject: Re: Sun supporting PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group