Re: Release Note Changes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Release Note Changes
Date: 2007-12-16 13:09:43
Message-ID: 200712161309.lBGD9hn22722@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavan Deolasee wrote:
> One of the improvements of HOT is to truncate a DEAD tuple to its
> line pointer. A DEAD tuple could be an old version of an updated
> tuple or a deleted tuple. When a tuple is truncated, the space used
> by the line pointer can not be reused (until the index entries are removed).
> But the space used by the actual tuple can be reused for a later update,
> after
> the page is defragmented. Note that this defragmentation can happen
> outside of a VACUUM.
>
> This gives us an ability to run VACUUM less frequently on a table. We
> still need to run VACUUM to remove the line pointer bloat, but may be less
> frequently for the given percentage of bloat. IMHO this should have a
> positive
> effect on performance atleast in an IO bound scenario.

I have updated the release note item title to mention DELETE as well:

Heap-Only Tuples (<acronym>HOT</>) accelerate space reuse for
most <command>UPDATE</>s and <command>DELETE</>s

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-12-16 14:04:29 Re: Document how to turn off disk write cache on popular operating
Previous Message Gregory Stark 2007-12-16 10:31:59 Re: pgwin32_open returning EINVAL