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

Re: Numeric 508 datatype

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Numeric 508 datatype
Date: 2005-11-17 16:20:50
Message-ID: 26770.1132244450@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-patches
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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2005-11-17 16:59:43
Subject: Re: Numeric 508 datatype
Previous:From: Andrew DunstanDate: 2005-11-17 16:13:06
Subject: Re: Numeric 508 datatype

pgsql-patches by date

Next:From: Simon RiggsDate: 2005-11-17 16:59:43
Subject: Re: Numeric 508 datatype
Previous:From: Andrew DunstanDate: 2005-11-17 16:13:06
Subject: Re: Numeric 508 datatype

pgsql-general by date

Next:From: Tom LaneDate: 2005-11-17 16:28:35
Subject: Re: Very slow queries on 8.1
Previous:From: Andrew DunstanDate: 2005-11-17 16:13:06
Subject: Re: Numeric 508 datatype

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