On 05/01/13 02:41, Neha Sharma wrote:
> Hi,
> 
> We are using slony to synchronise two postgres databases of two machines. 
> 
> Generally slony creates 6 connections with the database - 4 with local
> db and 2 with remote db.
> 
> But some problem is being observed on the machine having master db.
> Various slony remote connections are seen with the database.
> The limit of postgres connections is 100 and slony is consuming maximum
> connections due to which the db fails to respond after sometime. It was
> observed that connection reached to 104 out of which slony connections
> (which remote has created with db) were 74.
> We have to restart slony to clean all the connections.
> 
> Ideally there should only be 2 connections from the remote - one created
> by listener and another by worker thread.
> 
> There is no connectivity issue between the two machines.

This sounds very much like lost TCP connections that never get the FIN
or RST packts. Have you tried to enable keepalive with settings, that
let connections time out within 5 minutes or faster in both, the
PostgreSQL and the Slony configurations?


Jan

> 
> Could anyone please suggest what could be the reason for this weired
> behaviour of slony?
> Also, please tell if slony creates new connections without removing the
> older ones?
> 
> -- 
> */Neha Sharma/*
> 
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 


-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin