Re: Numeric 508 datatype

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
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>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Numeric 508 datatype
Date: 2005-11-17 16:59:43
Message-ID: 1132246783.4959.150.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

On Thu, 2005-11-17 at 11:20 -0500, 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.

If the patch is accepted technically, in can be applied at any time,
right up to code freeze for this or the next release. It's a fairly
independent patch.

I'd suggest we check it out now, then put it in a holding pen for awhile
to see if an upgrade tool emerges.

Best Regards, Simon Riggs

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2005-11-17 17:06:51 Re: Very slow queries on 8.1
Previous Message David Rysdam 2005-11-17 16:54:00 Re: Very slow queries on 8.1

Browse pgsql-hackers by date

  From Date Subject
Next Message mark 2005-11-17 17:31:17 Re: MERGE vs REPLACE
Previous Message Tom Lane 2005-11-17 16:20:50 Re: Numeric 508 datatype

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-11-17 17:48:45 Re: Numeric 508 datatype
Previous Message Tom Lane 2005-11-17 16:20:50 Re: Numeric 508 datatype