> Yeah, this is not a bug.
>
> At first, the standby performs an archive recovery until an invalid
> WAL record is found. Then it starts replication and tries to receive
> the missing WAL records from the primary. So such an error message
> would be logged whenever an invalid record is found and replication
> is started.
Can we improve the error message? Right now it's alarming people. Such as:
cannot stat
`/var/data1/pg_stuff/dump/replication_archive/000000010000000000000002':
End of Log
Of course, it would be even better to supress this error message
entirely unless the user is at DEBUG1 or better.
--Josh Berkus
