Re: 7.2.3?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)atentus(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Justin Clift <justin(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 7.2.3?
Date: 2002-09-29 04:47:44
Message-ID: 8211.1033274864@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)atentus(dot)com> writes:
> What would that converter need:
> [snip]
> I think that should be enough for converting table files. I'd like to
> experiment with something like this when I have some free time. Maybe
> next year...

It's difficult to say anything convincing on this topic without a
specific conversion requirement in mind.

Localized conversions like 7.3's tuple header change could be done on a
page-by-page basis as you suggest. (In fact, one reason I insisted on
putting in a page header version number was to leave the door open for
such a converter, if someone wants to do one.)

But one likely future format change for user data is combining parent
and child tables into a single physical table, per recent inheritance
thread. (I'm not yet convinced that that's feasible or desirable,
I'm just using it as an example of a possible conversion requirement.)
You can't very well do that page-by-page; it'd require a completely
different approach.

regards, tom lane

In response to

  • Re: 7.2.3? at 2002-09-29 04:31:38 from Alvaro Herrera

Responses

  • Re: 7.2.3? at 2002-09-29 08:08:35 from Hannu Krosing

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2002-09-29 04:54:30 Re: v7.3 Branched ...
Previous Message Tom Lane 2002-09-29 04:35:53 Re: [SQL] CURRENT_TIMESTAMP