Re: Avoiding unnecessary reads in recovery

> 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