Wed May 16 09:20:02 PDT 2007
- Previous message: [Slony1-general] Slony on windows wireless hangs.
- Next message: [Slony1-general] Slony Replication Slow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 16, 2007 at 11:00:49AM -0400, Andrew Sullivan wrote: > On Wed, May 16, 2007 at 09:05:52AM -0400, Al Rosenthal wrote: > > > My question, is there any way of adjusting settings to make slony > > more tolerant? Or am I looking in the wrong direction? I know I > > Slony is just using standard PostgreSQL connections. So your problem > basically comes down to your connection failing and not picking up > where it left off. This suggests to me that the network isn't really > working the way it ought to be. The connection is not just getting > interrupted, but the reconnection seems not to be picking back up the > same connection, which means that you don't get TCP retries and the > like. What happens in that case is that you have to wait for the TCP > timeout to happen, at which point Postgres will notice the connection > broke. You could lower that timeout in the operating system, I > suppose. The tcp_keepalives_* configuration parameters allow you to do this easily from within PostgreSQL (I think they're new it 8.2). -- Jim C. Nasby, Database Architect decibel at decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
- Previous message: [Slony1-general] Slony on windows wireless hangs.
- Next message: [Slony1-general] Slony Replication Slow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list