> on the master postgresql.conf I set
> listen_address = '*'
> wav_level = hot_standby
> max_wal_senders = 3
>
> I didn't change any of postgresql.conf Archiving settings. They all seem
> to be commented out. Could that be the problem?
>
> Evan
>
>
> O
Do not rsync the pg_xlog. Basically that error means that the
restore_command in your recovery.conf is not working. You have hot_standby
archiving going on the master and a recovery_command on the slave, right?
On Thu, Oct 13, 2011 at 10:41 AM, Evan Walter
wrote:
>
>
> Hello,
> I am somewhat n
There is also http://bucardo.org/wiki/Check_postgres but I haven't been able
to get it to work for monitoring replication. I am using a similar custom
script as Mahlon, but written in perl. Looking at Mahlon's code has shown
me an error in how I have been thinking about calculating the replicatio
It is possible. See
http://www.postgresql.org/docs/9.0/interactive/high-availability.html
On Wed, Oct 12, 2011 at 3:31 AM, Condor wrote:
> Hello everyone,
> from a few days I want to ask how to make replica server of my database and
> when spontaneously my master server going down due to loosi
There are also times when both are behind by quite a few thousand. Any
ideas on what might be causing these or how to try to catch the culprit?
Thanks.
--
Mark Keisler <http://my.mot-mobility.com/portal/site/people?coreid=qa4437>
<http://my.mot-mobility.com/portal/site/people?coreid=qa
