Re: TCP keepalive support for libpq - Mailing list pgsql-hackers

From Tollef Fog Heen
Subject Re: TCP keepalive support for libpq
Date
Msg-id 87mxzg8cpz.fsf@qurzaw.linpro.no
Whole thread Raw
In response to Re: TCP keepalive support for libpq  (daveg <daveg@sonic.net>)
Responses Re: TCP keepalive support for libpq
Re: TCP keepalive support for libpq
List pgsql-hackers
]] daveg 

| I disagree. I have clients who have problems with leftover client connections
| due to server host failures. They do not write apps in C. For a non-default
| change to be effective we would need to have all the client drivers, eg JDBC,
| psycopg, DBD-DBI, and the apps like psql make changes to turn it on. Adding
| this option as a non-default will not really help.

FWIW, this is my case.  My application uses psycopg, which provides no
way to get access to the underlying socket.  Sure, I could hack my way
around this, but from the application writer's point of view, I have a
connection that I expect to stay around and be reliable.  Whether that
connection is over a UNIX socket, a TCP socket or something else is
something I would rather not have to worry about; it feels very much
like an abstraction violation.

-- 
Tollef Fog Heen 
UNIX is user friendly, it's just picky about who its friends are


pgsql-hackers by date:

Previous
From: Priit Laes
Date:
Subject: Re: [PATCH] Output configuration status after ./configure run.
Next
From: Robert Haas
Date:
Subject: Re: TCP keepalive support for libpq