| From: | David Boreham <david_list(at)boreham(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: zero_damaged_pages doesn't work |
| Date: | 2010-09-27 22:45:32 |
| Message-ID: | 4CA11E8C.7040104@boreham.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/27/2010 4:40 PM, Jeff Davis wrote:
> It does zero the page in the buffer, but I don't think it marks it as
> dirty. So, it never really makes it to disk as all-zeros.
Ah ha ! This is certainly consistent with the observed behavior.
> zero_damaged_pages is not meant as a recovery tool. It's meant to allow
> you to pg_dump whatever data is not damaged, so that you can restore
> into a fresh location.
It'd be useful for future generations if this were included in the doc.
The latest version :
http://www.postgresql.org/docs/9.0/static/runtime-config-developer.html
still talks about destroying data (which at least to me implies a
persistent change
to the on-disk bits) and fails to mention that the zeroing only occurs
in the
page pool sans write-back.
If it helps, I'd be happy to contribute some time to fix up the docs,
but imho a simple
copy/paste of your text above would be sufficient.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Satoshi Nagayasu | 2010-09-27 22:51:35 | Re: ECPG - Some errno definitions don't match to the manual |
| Previous Message | Jeff Davis | 2010-09-27 22:40:28 | Re: zero_damaged_pages doesn't work |