Hey,
Using these steps to for archiving and HA:
Node1 : current master .. Node2 : current standby
On master in (postgresql.conf):
archive_mode = on
archive_command = 'test ! -f /data/pgsql/archivedir/%f cp %p
/data/pgsql/archivedir/%f'
archive_timeout = 3600
Note : I sync
Hi all,
I tried to setup up Master to standby switch but even though i am using
archiving to bump up time lines,
I noticed that Streaming replication gets setup between new standby and new
master but it stops after some time and doesn't start after that.
Following are the logs found in
On Mon, Jun 3, 2013 at 9:43 PM, prakhar jauhari prak...@gmail.com wrote:
and they just continue like this.
Please help me with the reason for this issue.
Can you provide exact steps you have used to setup up Master to
standby switch? That might help reproducing the problem and provide
some
On Wed, May 15, 2013 at 3:12 PM, prakhar jauhari prak...@gmail.com wrote:
So to allow a standby to recover WAL files that are missing (using archives
or directly copying wall from the new master to the new standby) in order to
complete the timeline change, is a wrong approach, I mean is this
So to allow a standby to recover WAL files that are missing (using archives
or directly copying wall from the new master to the new standby) in order
to complete the timeline change, is a wrong approach, I mean is this not
safe in term of data not being corrupted? Because i tried this and this
I think that you need to create a new base backup from the new master to
make the old master a standby server. I usually do this using rsync, so
that it takes as fast as possible, but you could also use a tool like
http://www.repmgr.org/
Regards,
Strahinja
On Mon, May 13, 2013 at 9:23 AM,
