| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] HOT WIP Patch - version 2 |
| Date: | 2007-02-20 14:23:30 |
| Message-ID: | 200702201423.l1KENUq18139@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Pavan Deolasee wrote:
> When following a HOT-update chain from the index fetch, if we notice that
> the root tuple is dead and it is HOT-updated, we try to prune the chain to
> the smallest possible length. To do that, the share lock is upgraded to an
> exclusive lock and the tuple chain is followed till we find a
> live/recently-dead
> tuple. At that point, the root t_ctid is made point to that tuple. In order
I assume you meant recently-dead here, rather than live/recently-dead,
because we aren't going to change live ctids, right?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-20 14:24:00 | Re: ToDo: add documentation for operator IS OF |
| Previous Message | Tom Lane | 2007-02-20 14:23:13 | Re: [HACKERS] HOT WIP Patch - version 2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-20 14:30:44 | Re: correct format for date, time, timestamp for XML functionality |
| Previous Message | Tom Lane | 2007-02-20 14:23:13 | Re: [HACKERS] HOT WIP Patch - version 2 |