| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Zdenek Kotala" <Zdenek(dot)Kotala(at)sun(dot)com> |
| Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Greg Stark" <greg(dot)stark(at)enterprisedb(dot)com>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [WIP] In-place upgrade |
| Date: | 2008-11-05 21:05:53 |
| Message-ID: | 603c8f070811051305y3c185a61o2142fab2095c41a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Problem is how to move tuple from page to another and keep indexes in sync.
> One solution is to perform some think like "update" operation on the tuple.
> But you need exclusive lock on the page and pin counter have to be zero. And
> question is where it is safe operation.
But doesn't this problem go away if you do it in a transaction? You
set xmax on the old tuple, write the new tuple, and add index entries
just as you would for a normal update.
When the old tuple is no longer visible to any transaction, you nuke it.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-11-05 21:41:52 | Re: [WIP] In-place upgrade |
| Previous Message | Heikki Linnakangas | 2008-11-05 20:46:50 | Re: Toast bug in CVS HEAD |