From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
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 12:59:19 |
Message-ID: | 20070703125919.GA25897@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-07-03 13:11:17 | Re: Proposal: In-Place upgrade concept |
Previous Message | Zdenek Kotala | 2007-07-03 11:31:13 | Re: Proposal: In-Place upgrade concept |