On Dec 8, 2007, at 9:21 AM, Geoffrey wrote:
I am quite new to Slony as well, but one of the first requirements
the docs state is:
Thus, examples of cases where Slony-I probably won't work out well
would include:
* Sites where connectivity is really "flakey"
* Replication to nodes t
Pedro Doria Meunier wrote:
Hi All,
I would like to implement DB replication with Slony but with a slave
that will not be always available.
The master would have to check first of the slave's availability and
then start syncing...
Is this at all possible, or am I just raving? : )
I am quite ne
Hi All,
I would like to implement DB replication with Slony but with a slave
that will not be always available.
The master would have to check first of the slave's availability and
then start syncing...
Is this at all possible, or am I just raving? : )
Kind regards,
--
Pedro Doria Meunier
Ips d
Slawek wrote:
Hello,
I tring to set up Slony replication and am having issues with
repeatability.
Probably best to ask on the slony list..
http://gborg.postgresql.org/pipermail/slony1-general/
Sign up here: http://gborg.postgresql.org/mailman/listinfo/slony1-general
--
Postgresql & php tu
Hello,
I tring to set up Slony replication and am having issues with
repeatability.
Configuration: 2 nodes
Slony ver.: 1.2.6
OS: SuSE Linux 9.2
About 1/3 of the time, replication does not start properly. I think
I've traced it down to the fact that sometimes the second node is not
created pro
