to accept
Docs this exit code as a non-error case.
--
Sincerely,
Linas Virbalas
http://flyingclusters.blogspot.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
/00060066': No
such file or directory
Restoring 0007.history
mv: cannot stat `/opt/PostgreSQL/9.1/archive/0007.history': No such file
or directory
2011-09-23 09:52:31 CEST LOG: streaming replication successfully connected
to primary
--
Best regards,
Linas Virbalas
http
(without even
starting/stopping backup), the standby starts up successfully.
--
Hope this helps,
Linas Virbalas
http://flyingclusters.blogspot.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
But on the standby its size is the old one (thus, it seems, that the size
changed after the rsync transfer and before the pg_stop_backup() was
called):
Now that seems pretty weird - I don't think that file should ever shrink.
It seems, I was not clear in my last example. The pg_clog file
begins in the log?
Could you provide us with the exact rsync version and parameters you use?
rsync -azv
version 2.6.8 protocol version 29
--
Sincerely,
Linas Virbalas
http://flyingclusters.blogspot.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Hello,
* Context *
I'm observing problems with provisioning a standby from the master by
following a basic and documented Making a Base Backup [1] procedure with
rsync if, in the mean time, heavy load is applied on the master.
After searching the archives, the only more discussed and similar
