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 i
))
> the location at which replay begins when you fire up the clone.
As you have seen in my original message, in the pg_log I get only the
restored WAL file names after starting up the standby. Can I tune the
postgresql.conf to include the location at which replay begins in the log?
> Could you pr
recovery state reached at
0/6600
2011-09-23 09:52:31 CEST LOG: database system is ready to accept read only
connections
Restoring 00060066
mv: cannot stat `/opt/PostgreSQL/9.1/archive/00060066': No
such file or directory
Restoring 0007.history
mv:
1-09-23 14:33:46 CEST DETAIL: Could not read from file "pg_clog/" at
offset 8192: Success.
6. Now, if I do something that, of course, should never be done, and copy
this file from master to the standby soon enough (without even
starting/stopping backup), the standby starts up
>> 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 fi
uot;vanished source files", and you can write a driver script 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
