Re: FSM rewrite committed, loose ends - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: FSM rewrite committed, loose ends
Date
Msg-id 48E48132.9020502@enterprisedb.com
Whole thread Raw
In response to Re: FSM rewrite committed, loose ends  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: FSM rewrite committed, loose ends
List pgsql-hackers
Zdenek Kotala wrote:
> Heikki Linnakangas napsal(a):
>> The FSM is not updated during WAL replay. That means that after crash 
>> recovery, the FSM won't be completely up-to-date, but at roughly the 
>> state it was at last checkpoint. In a warm stand-by, the FSM will 
>> reflect the situation at last full backup. We need to think when the 
>> FSM should be updated during WAL replay. Probably not after every 
>> record, because of the overhead, but certainly more often than never.
> 
> What's about after a page write  during a WAL replay?

You mean when a page is evicted from the buffer cache? That might be 
pretty good from performance point of view, but from a modularity point 
of view, the buffer manager should have no business modifying the FSM.

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


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: FSM rewrite committed, loose ends
Next
From: "Dave Page"
Date:
Subject: Re: FSM rewrite committed, loose ends