David Boreham <david_list@xxxxxxxxxxx> writes: > On 9/27/2010 4:40 PM, Jeff Davis wrote: >> 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. The reason it tells you that data will be destroyed is that that could very well happen. If the system decides to put new data into what will appear to it to be an empty page, then the damaged data on disk will be overwritten, and then there's no hope of recovering anything. Like Jeff said, this is not a recovery tool. It's certainly not meant to be something that you keep turned on for any length of time, and so the possibility of repeat messages is really not a design consideration at all. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
