On 7/31/2006 6:28 PM, Christopher Browne wrote: > Andre Chagas de Miranda Reboucas wrote: >> Hi everyone, >> >> I'm building a HA solution with Slony-I + HeartBeat with 2 machines, and my >> goal is to create a script that should be able to start/stop Slony-I >> Replication in order to use it in my haresources file. >> >> My ideia was to gather all slony-I initialization scripts into a >> /etc/init.d/ script. So far my script is doing quite well in starting >> Slony-I, but I'm having troubles when I try to stop it. The problem is that, >> until now, I didn't find out other ways to stop Slony, unless killing slon >> or stoping postgres service. >> >> Does anyone has any tip of how to stop slony decently? >> >> Thanks a lot. >> > Simple answer: Go ahead, kill the slon process. > > That is how to get replication to stop. > > When we want to shut replication down, the script usually does something > like the following: > > kill -2 $PID > sleep 10 > kill -9 $PID > > e.g. - if the slon refuses to die, it puts it down hard...
... and since slon is a pure DB client application, all existing DB backends working on behalf of slon will simply lose the connection to their client, roll back and terminate. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] # _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
