On 4/19/07, Francisco Reyes <[EMAIL PROTECTED]> wrote:
Brian A. Seklecki writes: > The RC script is a good place to start if you have one instance. It doesn't seem like they started slony from the rc scripts. trying to call the script with stop gave me: slon not running? (check /var/run/slon.pid). Is it safe to kill the slon processes? ps ax | grep slon 82361 p0 R+ 0:00.00 grep slon 85957 p0- S 8:29.91 slon -f /usr/local/etc/slon.conf 99783 p0- I 0:00.03 slon -f /usr/local/etc/slon.conf
The slons may be running via daemontools, which will be very annoying and restart them automatically if you just kill them. Look for supervise processes with suspicious directory names if your slons come back to life. If service processes exist, then try the following. touch $dir/down # do not restart on boot svc -dx $dir $dir/log # shut it down now Others have provided ample advice on how to remove the slony stuff inside the database, but briefly, on the master DROP SCHEMA _my_slony_cluster CASCADE; On the slave, it's more complicated, but I doubt you care about the slave anyway so just drop the database and recreate it when / if you're ready. Note that postgres supports WAL file log shipping (and PITR), which is a relatively easy way to backup your database. Andrew
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
