| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Owen Hartnett | 2007-04-26 14:32:12 | Re: Schema as versioning strategy |
| Previous Message | Michael Meskes | 2007-04-26 13:03:50 | Re: ECPG failure on BF member Vaquita (Windows Vista) |