Re: Avoiding unnecessary reads in recovery - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Avoiding unnecessary reads in recovery
Date
Msg-id 145A884B-7335-416D-9E53-393A0A079325@decibel.org
Whole thread Raw
In response to Re: Avoiding unnecessary reads in recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Apr 26, 2007, at 3:39 PM, Tom Lane wrote:
> Jim Nasby <decibel@decibel.org> writes:
>> 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.
>
> One of the advantages of the proposed patch is that it avoids  
> having to
> make any assumptions like that.

Yeah, the only email in the thread when I wrote that was Heikki's  
original email (I wrote the email on a plane, but did note it had  
been some time after the original email with no replies). Sorry for  
the noise.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Avoiding unnecessary reads in recovery
Next
From: Chris Browne
Date:
Subject: Re: Modifying TOAST thresholds