| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [WIP] In-place upgrade |
| Date: | 2008-11-05 05:51:41 |
| Message-ID: | 4911346D.3040200@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
> "Robert Haas" <robertmhaas(at)gmail(dot)com> writes:
> An old page which never goes away. New page formats are introduced for a
> reason -- to support new features. An old page lying around indefinitely means
> some pages can't support those new features. Just as an example, DBAs may be
> surprised to find out that large swathes of their database are still not
> protected by CRC checksums months or years after having upgraded to 8.4 (or
> even 8.5 or 8.6 or ...). They would certainly want a way to ensure all their
> data is upgraded.
Then provide a manual mechanism to convert all pages?
Joshua D. Drake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-11-05 06:04:41 | Re: [WIP] In-place upgrade |
| Previous Message | Gregory Stark | 2008-11-05 05:11:03 | Re: [WIP] In-place upgrade |