03.07.2013, 13:14, "Stefano Sasso" <stesa...@gmail.com>:
2013/7/3 Andrey Groshev <gre...@yandex.ru>03.07.2013, 12:30, "Stefano Sasso" <stesa...@gmail.com>:2013/7/3 Andrey Groshev <gre...@yandex.ru>03.07.2013, 11:42, "Stefano Sasso" <stesa...@gmail.com>:Does "standby" mean that PostgreSQL is stopped ?If Master doesn't have WAL files which new slave needs,
new slave can't connect master.
How do you solve it ?
copy data or wal-archive on start automatically ?
It may cause timed-out if PostgreSQL has large database.I'm using streaming replication.This is understandable, it is not clear what your "slave" is different from "standby".slave is syncronized with streaming replication,standby do a sync on daily basis (so if both master and slave fails, I lose only one day of data - not a problem).I would call it a "backup" :)yeah, but a standby can become a master or a slave ;)
What is the profit?
The third node is connected to the Master every day?
But first, it will be synchronized through the "WAL" files.
Instead of spread the load during the day you'll get a peak load.
Or I missing something in your architecture?
,_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
