Re: Proposal: Multiversion page api (inplace upgrade)

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Zdenek Kotala" <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: Multiversion page api (inplace upgrade)
Date: 2008-06-11 14:59:06
Message-ID: 484FE83A.1000602@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala wrote:
> 4) Implementation
>
> The main point of implementation is to have several version of
> PageHeader structure (e.g. PageHeader_04, PageHeader_03 ...) and correct
> structure will be handled in special branch (see examples).

(this won't come as a surprise as we talked about this in PGCon, but) I
think we should rather convert the page structure to new format in
ReadBuffer the first time a page is read in. That would keep the changes
a lot more isolated.

Note that you need to handle not only page header changes, but changes
to internal representations of different data types, and changes like
varvarlen and combocid. Those are things that have happened in the past;
in the future, I'm foreseeing changes to the toast header, for example,
as there's been a lot of ideas related to toast options compression.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-06-11 15:15:06 Re: Proposal: Multiversion page api (inplace upgrade)
Previous Message Tom Lane 2008-06-11 14:56:08 Re: Proposal: Multiversion page api (inplace upgrade)