Re: Requesting clarification on Vacuuming/Freezing behaviour - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Re: Requesting clarification on Vacuuming/Freezing behaviour
Date
Msg-id 9362e74e0712170526h64f8e9eka2779ab57ff22b74@mail.gmail.com
Whole thread Raw
In response to Re: Requesting clarification on Vacuuming/Freezing behaviour  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Thanks Heikki. I misunderstood things. Especially the comment in log_heap_freeze misled me.

On Dec 17, 2007 1:39 PM, Heikki Linnakangas <heikki@enterprisedb.com > wrote:
Gokulakannan Somasundaram wrote:
> a) When i was looking at the code for freezing heap tuples, i found out the
> following. While freezing we log the complete block(not just the tuples we
> froze).
> b) Again after removing the dead tuples and fragmentation, we log the
> complete block.

Umm, no we don't. In log_heap_freeze, we log an array of offsets, of
those tuples that were frozen.

Perhaps you're been confused by full page writes? If a block hasn't been
modified by last checkpoint, then we do log the whole page for any
operation, including vacuuming and freezing. (except setting hint bits).

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com



--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Group.
(www.alliedgroups.com)

pgsql-hackers by date:

Previous
From: "Gokulakannan Somasundaram"
Date:
Subject: Re: Proposal for Null Bitmap Optimization(for Trailing NULLs)
Next
From: Andrew Dunstan
Date:
Subject: Re: Proposal for Null Bitmap Optimization(for Trailing NULLs)