| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Avoiding unnecessary reads in recovery |
| Date: | 2007-04-27 17:59:24 |
| Message-ID: | 145A884B-7335-416D-9E53-393A0A079325@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 26, 2007, at 3:39 PM, Tom Lane wrote:
> Jim Nasby <decibel(at)decibel(dot)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(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2007-04-27 18:55:41 | Re: Modifying TOAST thresholds |
| Previous Message | Simon Riggs | 2007-04-27 17:45:38 | Re: Avoiding unnecessary reads in recovery |