| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hannu Krosing" <hannu(at)skype(dot)net>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>, "Nikhil S" <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
| Subject: | Re: HOT for PostgreSQL 8.3 |
| Date: | 2007-02-12 11:41:30 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57901C13537@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > What are the problems with just shuffling the last (and only
visible)
> > > tuple to replace the HOT-hain root and be done with it ?
> >
> > ctid stops being a reliable identifier.
A backend selecting the row by ctid would need to take one step to
the root slot to get at the tuple. This does seem possible if the
tuples got swapped.
The old "current version" slot would need to become RECENTLY_DEAD
and could not be removed right away. It also needs a flag to
denote that the one step is necessary.
It sure would be nice if a root could be reused during regular vacuum,
(even if it were only possible under very restricted conditions,
that eventually apply).
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-02-12 14:05:30 | Re: select from sequences |
| Previous Message | Edwin Eyan Moragas | 2007-02-12 09:42:25 | Re: Priorities for users or queries? |