From: | "Nico" <Nicolas(dot)PAYART(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Restarting Slony crashes Postgresql? |
Date: | 2006-08-16 07:58:53 |
Message-ID: | 1155715133.823956.92710@m79g2000cwm.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi group,
I'm using Slony-I 1.1.5 with Postgresql 8.1.4 on 3 DB server (OS =
debian sarge).
I set a replication from a database on server A (master) to 2 servers B
and C (slaves).
Note that the slaves databases are in production and have a quite big
load.
I noticed last day that when I stop Slony daemon (for any reason) on a
slave server (B or C), a few seconds later, the server doesn't respond
anymore. Then I need to reboot the system. I noticed some "fetch 100
from LOG" queries on the master database too...
=> To prevent the server crashing, It seems that I need to restart
postgresql just after restarting Slony (and before it all crashes).
Is it always necessary to restart Postgresql after restarting a Slony
daemon ? (though, it doesn't seem necessary when the servers have not
many connections)
Any information will be appreciated.
Regards,
Nico
From | Date | Subject | |
---|---|---|---|
Next Message | Julian Scarfe | 2006-08-16 09:18:03 | Timezones -- what comes out does not go in? |
Previous Message | craigp | 2006-08-16 07:02:31 | limitations of constraints, possible bugs |