Skip site navigation (1) Skip section navigation (2)

Requesting clarification on Vacuuming/Freezing behaviour

From: "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com>
To: "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>
Subject: Requesting clarification on Vacuuming/Freezing behaviour
Date: 2007-12-17 07:47:21
Message-ID: 9362e74e0712162347g65ef8165wbe5dc6fd514539ff@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,
    I got some time to relook at the index with the snapshot patch. Still i
need to complete the freezing of index tuples with the snapshot.
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.

As i understand, Vacuum is one atomic operation. Why do we need to make this
extra protection for Freezing?
I think the fix should be very simple. Before logging the Frozen block, we
need to check whether there are any dead tuples removed from it..

Please clarify on whether i am missing something important..

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

Responses

pgsql-hackers by date

Next:From: Gokulakannan SomasundaramDate: 2007-12-17 08:02:54
Subject: Re: Proposal for Null Bitmap Optimization(for Trailing NULLs)
Previous:From: Gokulakannan SomasundaramDate: 2007-12-17 07:40:48
Subject: Proposal for Null Bitmap Optimization(for Trailing NULLs)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group