Ireneusz Pluta <[email protected]> writes:
> - when playing with pg_filedump I noticed that last pages of the table
> are always initially reported as damaged, as they come, then, as newer
> pages get allocated and filled, these initially bad pages "become
> valid", as in the following example repeating the same pg_filedump.
This doesn't seem terribly surprising. A newly-added page on disk will
be initially filled with zeroes, which I think pg_filedump will complain
about. It won't get overwritten with "valid" data until the page is
next written, either because of a checkpoint or because the buffer space
is needed for another page. pg_filedump can't see the state of the page
within the server's buffers, which is what counts here.
regards, tom lane
--
Sent via pgsql-admin mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
