| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: HOT WIP Patch - Version 5.0 |
| Date: | 2007-03-21 15:56:04 |
| Message-ID: | 1174492564.6069.35.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2007-03-21 at 11:27 +0530, Pavan Deolasee wrote:
> The version 5.0 of HOT WIP patch is posted on pgsql-patches. This
> fixes the VACUUM FULL issue with HOT. In all the earlier versions,
> I'd disabled VACUUM FULL.
>
> When we move the HOT-chain, we move the chains but don't carry
> the HOT_UPDATED or HEAP_ONLY flags and insert as many index
> entries as there are tuples in the chain. IOW the HOT-update
> is actually turned into a COLD chain.
Seems fine to me.
> Apart from this, I'd to make some changes to the VACUUM FULL
> code so that the number of indexed tuples is counted
> correctly. With HOT, whenever a HEAP_ONLY tuple is moved, an
> additional index entry is generated and this needs to be
> taken into account.
It should do this, but its probably worth posting a TODO of minor items
like this, otherwise we'll lose focus on the major items.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-03-21 15:59:22 | Re: CREATE INDEX and HOT - revised design |
| Previous Message | Shane Ambler | 2007-03-21 15:47:32 | Re: Money type todos? |