| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "Pavan Deolasee" <pavan(at)enterprisedb(dot)com>, Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: HOT + MVCC-safe cluster conflict fix |
| Date: | 2007-04-19 13:18:33 |
| Message-ID: | 2e78013d0704190618i186ae8c9m4112af8deec9fb16@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On 4/19/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
>
> Hi Pavan,
>
> Here's a little patch against CVS HEAD + NewHOT-v7.0.patch to fix the
> conflict between MVCC-safe cluster and HOT.
>
> index_getnext is modified to return all tuples in a HOT chain when
> called with SnapshotAny. Cluster will insert them all as normal cold
> updates.
>
>
Thanks Heikki. We might need to tweak it a bit because I think I had
made an assumption that heap_hot_fetch() should be called only on
the root tuple. Anyways, would look at it.
Thanks
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-04-19 13:23:48 | Re: HOT Patch - Ready for review |
| Previous Message | Heikki Linnakangas | 2007-04-19 12:16:32 | HOT + MVCC-safe cluster conflict fix |