On 13/01/14 17:50, Mike Broers wrote:
> 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?
This presentation:
http://www.youtube.com/watch?v=TovZ0lb16-Q
suggests pg_filedump.
Torsten
Thanks for the responses, that clarifies the checksum feature for me.
FWIW, my pgbench tests between a 9.2 server and a 9.3 server with checksum
showed very similar performance characteristics and system resource
utilization. Im going to set up another load test with our actual
application to see
On Tue, Jan 14, 2014 at 1: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
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 i
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
