From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | David Boreham <david_list(at)boreham(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: zero_damaged_pages doesn't work |
Date: | 2011-02-01 21:44:51 |
Message-ID: | 201102012144.p11Lipj17478@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
David Boreham wrote:
> On 9/27/2010 4:53 PM, Tom Lane wrote:
> > The reason it tells you that data will be destroyed is that that could
> > very well happen.
>
> Re-parsing this, I think there was a mis-communication :
>
> I'm not at all suggesting that the doc should _not_ say that data will
> be corrupted.
> I'm suggesting that in addition to what it currently says, it also
> should say that the on-disk data won't be
> changed by the page zeroing mode.
>
> In my searching I found countless people over the past few years who had
> been similarly confused into believing that it would write back the
> zeroed page
> to disk.
Based on this discussion from September, I have applied the attached
documentation patch to clarify that zero_damaged_pages are not forced to
disk, and when to set this parameter off again.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/zero.diff | text/x-diff | 2.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2011-02-01 21:59:02 | Re: Windows to Linux PostgreSQL Migration |
Previous Message | Alban Hertroys | 2011-02-01 21:32:52 | Re: Issues with generate_series using integer boundaries |