Thread: HotStandby --Advice needed

Configured server1 to be primary archiving on and server2 as standby with
base backup(only first time) to replicate from primary. If Primary(server1)
is down standby(server2) is configured as primary and starts archiving to
the same WAL archive.

If the previous primary(Server1) comes up it will be configured as standby
and one time recovery is done using restore_command from WAL archive (This
is done to speed up streaming replication if there is huge gap).

*This switching of roles continues... Is there any problem with this
procedure ?? *

Primary server postgresql conf settings:

max_wal_senders = 5
wal_level = hot_standby
archive_mode = on
archive_command = 'copy %p $DBstreamshare\\%f'
wal_keep_segments = 32
replication_timeout = 0

Standby server postgresql conf settings:
max_standby_streaming_delay = 30s
hot_standby = on
standby recovery.conf settings:
standby_mode = 'on'
restore_command = 'copy $DBstreamshare\\%f %p'
primary_conninfo = 'host=$Primaryserver port=5432 user=postgres'



--
View this message in context: http://postgresql.1045698.n5.nabble.com/HotStandby-Advice-needed-tp5708740.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Adding to the previous question

Should recovery in the standby using restore_command is done only with
base_backup which was taken for the first time

or

It can be at any point of time on standby is recovered using restore_command
??



--
View this message in context: http://postgresql.1045698.n5.nabble.com/HotStandby-Advice-needed-tp5708740p5708746.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.