| From: | "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Requesting clarification on Vacuuming/Freezing behaviour |
| Date: | 2007-12-17 13:26:04 |
| Message-ID: | 9362e74e0712170526h64f8e9eka2779ab57ff22b74@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)enterprisedb(dot)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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-12-17 13:47:54 | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |
| Previous Message | Gokulakannan Somasundaram | 2007-12-17 13:24:34 | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |