On Wed, 2013-04-03 at 09:48 -0700, Jeff Janes wrote:
> And why did those uninitialized pages trigger warnings when they were
> autovacced, but not when they were seq scanned in a query?
>
A scan won't trigger that warning. Empty pages are sometimes the
expected result of a crash when the file is extended but the page is not
written yet. So empty pages aren't necessarily an indication of
corruption (though I'd like to fix that eventually, because sometimes
zeroing is corruption).
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
