From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: In-Place upgrade concept |
Date: | 2007-07-03 13:11:17 |
Message-ID: | 468A4AF5.1080201@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
> On Tue, Jul 03, 2007 at 12:05:07PM +0100, Heikki Linnakangas wrote:
>>> This is actually a bit of a problem. We would need to know when we
>>> read in a page what the tupledescriptor for that relation looks like
>>> to know which fields are varlena. I'm not sure how easy it would be
>>> to arrange for the tuple descriptor to be passed down that far.
>> Speaking of on-the-fly upgrading, ReadBuffer is already passed the
>> Relation, which contains the TupleDesc, so I don't think that's a
>> problem. Not sure how easy that would be to do in an external program
>> like pg_migrator.
>
> My reading of this thread so far is that we're intending to upgrade
> pages on the fly? Which means that at any point in time, some pages
> will be converted and some not, so the tuple descriptor isn't going to
> help, surely you need some identifier on the page telling you if it's
> upgraded or not?
Yes, we already have such an identifier. The page layout version number
is stored on every page.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2007-07-03 13:28:06 | Re: Proposal: In-Place upgrade concept |
Previous Message | Martijn van Oosterhout | 2007-07-03 12:59:19 | Re: Proposal: In-Place upgrade concept |