Mon Aug 23 10:39:42 PDT 2010
- Previous message: [Slony1-bugs] [Bug 104] slon core in sched_add_fdset
- Next message: [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=126 --- Comment #3 from Steve Singer <ssinger at ca.afilias.info> 2010-08-23 10:39:43 PDT --- No that controls server side keep alives, we want client side keep alives. This was actually introduced in 9.0, see http://www.postgresql.org/docs/9.0/static/libpq-connect.html#LIBPQ-KEEPALIVES Prior to 9.0 applications like slony could call PQSocket and get then manually adjust values on the socket which is what we will have to do if we want the feature when running against older versions of PG. In either case we need to setup a system that replicates a slon detected socket failure to make sure we don't have some other horrible issue waiting in the code path that gets hit once the keep socket times out. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 104] slon core in sched_add_fdset
- Next message: [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list