Re: Page-level version upgrade (was: Block-level CRC checks)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: decibel <decibel(at)decibel(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Page-level version upgrade (was: Block-level CRC checks)
Date: 2009-12-02 02:16:48
Message-ID: 603c8f070912011816n29ebb302pba93032c387fd0c3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 1, 2009 at 5:15 PM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> On Tue, Dec 1, 2009 at 9:58 PM, decibel <decibel(at)decibel(dot)org> wrote:
>> What happened to the work that was being done to allow a page to be upgraded
>> on the fly when it was read in from disk?
>
> There were no page level changes between 8.3 and 8.4.

That's true, but I don't think it's the full and complete answer to
the question. Zdenek submitted a page for CF 2008-11 which attempted
to add support for multiple page versions. I guess we're on v4 right
now, and he was attempting to add support for v3 pages, which would
have allowed reading in pages from old PG versions. To put it
bluntly, the code wasn't anything I would have wanted to deploy, but
the reason why Zdenek gave up on fixing it was because several
community members considerably senior to myself provided negative
feedback on the concept.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-12-02 02:31:20 Re: Page-level version upgrade (was: Block-level CRC checks)
Previous Message KaiGai Kohei 2009-12-02 02:07:19 Re: SE-PgSQL patch review