From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Mike Broers <mbroers(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: question about checksum in 9.3 |
Date: | 2014-01-14 01:06:16 |
Message-ID: | 52D48D88.1070909@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/13/2014 08:50 AM, Mike Broers wrote:
> Hello, I am in the process of planning a 9.3 migration of postgres and I
> am curious about the checksum features available. In my test 9.3
> instance it seemed like this feature provides a log entry of the exact
> database/oid of the corrupt object when it is accessed, but not much
> else. I can't find much documentation on anything else this feature
> provides.
>
> Is there a built-in method of scanning the server to check for
> corruption or will I have to wait for a corrupt object to be accessed to
> see the log entry? Is there a relation that stores last checksum status
> or anyway of reporting on what objects are identified by postgres as
> corrupt or not corrupt?
>
> Are there any other features of the checksum I am missing besides the
> log entry?
I could not find anything and the reasons for that would seem to a
result of this sentence:
"The checksum is not valid at all times on a data page!!"
from the below where the gory details are laid out:
src/backend/storage/page/README
>
> Thanks
> Mike
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-01-14 01:11:11 | Re: question about checksum in 9.3 |
Previous Message | Adrian Klaver | 2014-01-14 00:35:47 | Re: pg_restore - table restoration |