I am trying an new configuration and was wondering if it is valid. We have
three PostgreSQL servers (DB1, DB2 and DB3). DB1 is currently the master with
DB2 and DB3 setup as hot_standby using streaming WAL. DB2 is the backup in case
DB1 fails. A virtual IP managed by Pacemaker moves between DB1
On Mon, Jun 17, 2013 at 8:14 AM, Keith Ouellette
wrote:
> I got the initial WAL replication going between DB1 and DB2 and between the
> virtual IP (currently on DB1) and DB3. So far all is well. However, If I
> simulate a failover to DB2 (promote DB2 and move the virtual IP to it), WAL
> does not
Hey..
I am facing a similar kind of problem, but in a two node setup. Streaming
replication is being used with a high wal_keep_segments, using log shipping
to bump up timelines on the standby server to setup SR(streaming
replication).
DB1 - master
DB2 - standby
When a switchover happens DB2 becom
prakhar jauhari wrote:
> I am facing a similar kind of problem, but in a two node setup. Streaming
> replication is being used
> with a high wal_keep_segments, using log shipping to bump up timelines on the
> standby server to setup
> SR(streaming replication).
> DB1 - master
>
> DB2 - standby
>
Hi,
Ya the error logs came, but only when the DB1 was corrupted. Here is a
excerpt from the logs.
*LOG: database system was shut down at 2013-06-19 09:40:55 UTC
LOG: restored log file "0004.history" from archive
cp: cannot stat `/data/pgsql/archivedir/0005.history': No such file or
dire
On Tue, Jun 18, 2013 at 11:20 PM, prakhar jauhari wrote:
> When a switchover happens DB2 becomes the new master and when DB1 comes up
> it will act as the standby to the new master (.history files from new master
> are copied to DB1 to bump up its timeline so as to setup SR). DB1 is not
> recreate
