> 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.
In response to
pgsql-hackers by date
|Next:||From: Owen Hartnett||Date: 2007-04-26 14:32:12|
|Subject: Re: Schema as versioning strategy|
|Previous:||From: Michael Meskes||Date: 2007-04-26 13:03:50|
|Subject: Re: ECPG failure on BF member Vaquita (Windows Vista)|