Re: [GENERAL] Slony replication
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 that are unpredictably connected. So I suspect Slony is not a solution for your effort. See: If your DB doesn't change very much (like a few hundred or thousand update/insert/delete per day), then slony can work just fine in such a batch mode. Things break down when you accumulate several hundred thousand or more changes between times when you're connected. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] Slony replication
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 da Olaria Edf. Jardins do Garajau, 4 r/c Y 9125-163 Caniço Madeira Portugal GSM: +351 96 17 20 188 Skype: pdoriam http://www.madeiragps.com signature.asc Description: This is a digitally signed message part
Re: [GENERAL] Slony replication
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 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 that are unpredictably connected. So I suspect Slony is not a solution for your effort. See: http://slony.info/documentation/slonyintro.html#INTRODUCTION -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[GENERAL] Slony Replication problem
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 properly in the prime db. I can see this by querying the
sl_node table where only 1 node (the prime) appears. On the backup
db, both nodes appear properly. To create the node, I'm using the
following slonik script
try {
echo 'Storing node 2';
store node (id = 2, comment = 'Node 2');
}
on error {
echo 'Could not create Node 2!';
exit -1;
}
No error is thrown when this code is ran, so as far as slonik script
is concerned everything is OK.
Questions:
1) What could be causing the second node to fail to be created? If
this is a timing issue, is there an event, or some data, I could check
to make sure that the 2nd node is ready to be created?
2) I discover that this error has occured after Slony is started on
both servers, and the replication set is subscribed to. If I have to
recreate this 2nd node on the prime server, what do I have to do?
Thank you,
Slawek
---(end of broadcast)---
TIP 6: explain analyze is your friend
Re: [GENERAL] Slony Replication problem
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 tutorials http://www.designmagick.com/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
