unexpected pageaddr

Well this reproduces with pg_basebackup

Disturbing. I wonder what else if lurking around

On Aug 2, 2017, at 10:34 PM, armand pirvu <armand.pirvu@gmail.com> wrote:

Hi

Setting up the hot_standby the only way I could it get the base remote cluster running was including pg_xlog
Now using rsync as opposed to pg_basebackup seems ok aka

psql postgres -c "select pg_start_backup('backup')"
rsync -a /var/lib/pgsql/9.5/data postgres@192.168.5.252:/var/lib/pgsql/9.5
psql postgres -c "select pg_stop_backup()"

But

cp: cannot stat ‘/var/lib/pgsql/pg_xlog_archive/000000010000000000000078’: No such file or directory
< 2017-08-02 22:30:40.949 CDT >LOG: unexpected pageaddr 0/3D000000 in log segment 000000010000000000000078, offset 0

and later

cp: cannot stat ‘/var/lib/pgsql/pg_xlog_archive/000000010000000000000079’: No such file or directory
< 2017-08-02 22:30:40.949 CDT >LOG: unexpected pageaddr 0/3D000000 in log segment 000000010000000000000079, offset 0
cp: cannot stat ‘/var/lib/pgsql/pg_xlog_archive/000000010000000000000079’: No such file or directory

Things seem okay but the unexpected pageaddr error is a bit unsettling .

Any thougts ? Something to be really worried about ? Did I miss it again ? :))

Thanks
Armand

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general