Re: Requesting clarification on Vacuuming/Freezing behaviour
| От | Gokulakannan Somasundaram |
|---|---|
| Тема | Re: Requesting clarification on Vacuuming/Freezing behaviour |
| Дата | |
| Msg-id | 9362e74e0712170526h64f8e9eka2779ab57ff22b74@mail.gmail.com обсуждение |
| Ответ на | Re: Requesting clarification on Vacuuming/Freezing behaviour (Heikki Linnakangas <heikki@enterprisedb.com>) |
| Список | pgsql-hackers |
Thanks Heikki. I misunderstood things. Especially the comment in log_heap_freeze misled me.
--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Group.
(www.alliedgroups.com)
On Dec 17, 2007 1:39 PM, Heikki Linnakangas <heikki@enterprisedb.com > wrote:
Gokulakannan Somasundaram wrote:Umm, no we don't. In log_heap_freeze, we log an array of offsets, of
> 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.
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 по дате отправления: