Skip site navigation (1) Skip section navigation (2)

Re: Avoiding unnecessary reads in recovery

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Jim Nasby" <decibel(at)decibel(dot)org>,"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: "pgsql-hackers Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoiding unnecessary reads in recovery
Date: 2007-04-26 14:10:56
Message-ID: E1539E0ED7043848906A8FF995BDA57901F40487@m0143.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> So what happens if a backend is running with full_page_writes 
> = off, someone edits postgresql.conf to turns it on and 
> forgets to reload/ restart, and then we crash? You'll come up 
> in recovery mode thinking that f_p_w was turned on, when in 
> fact it wasn't.
> 
> ISTM that we need to somehow log what the status of 
> full_page_writes is, if it's going to affect how recovery works.

Optimally recovery should do this when confronted with a full page image
only. The full page is in the same WAL record that first touches a page,
so this should not need to depend on a setting.

Andreas

In response to

pgsql-hackers by date

Next:From: Owen HartnettDate: 2007-04-26 14:32:12
Subject: Re: Schema as versioning strategy
Previous:From: Michael MeskesDate: 2007-04-26 13:03:50
Subject: Re: ECPG failure on BF member Vaquita (Windows Vista)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group