Re: FSM rewrite committed, loose ends

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FSM rewrite committed, loose ends
Date: 2008-09-30 12:49:26
Message-ID: 48E22056.8060509@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-09-30 12:55:47 Re: parallel pg_restore - WIP patch
Previous Message Heikki Linnakangas 2008-09-30 12:45:48 Re: FSM rewrite committed, loose ends