From: | Sergei Georgiev <sergei(dot)georgiev(at)gmail(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Socket timeouts (probably) |
Date: | 2005-02-24 10:04:13 |
Message-ID: | b9e7d4a8050224020458cb6a3e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> You may want to try tweaking /proc/sys/net/ipv4/tcp_keepalive_* on the
> server to make TCP keepalives notice the dead connection faster (these
> are global settings, though). There are corresponding setsockopt() calls
> you could make on a per-socket basis if you are prepared to tweak the
> server code.
I'd rather not, because as Markus said there may be other services
started on the DB machine in the future (it's just a prototype testing
for a new project). I found that there is a property called
"statement_timeout" in the postgresql.conf. This limits the time, in
which a statement must be executed. It looks like a solution to me,
but I need to test it.
10x anyway :)
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2005-02-24 10:32:26 | Re: [postgis-devel] JDBC & WKB - 400% overhead |
Previous Message | Kris Jurka | 2005-02-24 10:02:34 | Re: [postgis-devel] JDBC & WKB - 400% overhead |