| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2005-11-18 11:13:00 | How to debug a locked backend ? |
| Previous Message | Wolfgang Keller | 2005-11-18 10:00:51 | Re: Sun supporting PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-11-18 11:32:07 | Re: Numeric 508 datatype |
| Previous Message | Zeugswetter Andreas DCP SD | 2005-11-18 10:45:33 | Re: Improving count(*) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aftab Alam | 2005-11-18 11:17:10 | trigger |
| Previous Message | Mark Kirkwood | 2005-11-18 05:30:11 | Re: TODO Item - Add system view to show free space map |