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

From Zdenek Kotala
Subject Re: FSM rewrite committed, loose ends
Date
Msg-id 48E22056.8060509@sun.com
Whole thread Raw
In response to FSM rewrite committed, loose ends  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: FSM rewrite committed, loose ends  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
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?
    Zdenek


-- 
Zdenek Kotala              Sun Microsystems
Prague, Czech Republic     http://sun.com/postgresql



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: FSM rewrite committed, loose ends
Next
From: Andrew Dunstan
Date:
Subject: Re: parallel pg_restore - WIP patch