| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org>, "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>, "Nikhil S" <nikhil(dot)sontakke(at)enterprisedb(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Subject: | Re: HOT for PostgreSQL 8.3 |
| Date: | 2007-02-07 20:38:08 |
| Message-ID: | 1170880688.3645.835.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2007-02-07 at 14:17 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > The basic idea is that when a tuple is UPDATEd we can, in certain
> > circumstances, avoid inserting index tuples for a tuple. Such tuples are
> > marked HEAP_ONLY_TUPLE, but their storage is otherwise identical to
> > other tuples.
>
> What is VACUUM FULL going to do when it wants to move one of these things?
This question stands out from the others. I'm not sure which aspect
you're thinking of - do you see some failure cases?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-02-07 20:57:50 | Re: HOT for PostgreSQL 8.3 |
| Previous Message | Tom Lane | 2007-02-07 20:37:24 | Re: [PATCHES] writing new regexp functions |