From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dirk Niggemann <dirk-n@dircon.co.uk>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] timeouts in libpq- can libpq requests block forever/a very long time?
Date: Sat, 02 Oct 1999 14:43:22 -0400
Message-ID: <8248.938889802@sss.pgh.pa.us> (raw)
In-Reply-To: <37F64B68.60868E33@dircon.co.uk>
Dirk Niggemann <dirk-n@dircon.co.uk> writes:
> Would there be any problems with changing pqWait so it uses a timeout?
I think this would be rather risky: if I issue a query that the backend
takes a long time to compute, I don't want libpq timing out on me,
*especially* not if its response is to close the connection rather than
some fail-soft recovery technique. If the timeout is
application-settable and defaults to infinity, it might be OK.
In my own applications using the asynchronous query features, I have not
seen any actual hangups that could be improved by a timeout ... but I've
mostly been working across LAN rather than WAN connections...
> I would also like to add a timeout for the connect operation on the
> socket-
> on a sufficiently frazzled WAN this could block for a long time-
This might be useful, but again I wonder whether libpq ought to be
second-guessing the transport system about how long is reasonable to
wait for a response.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, dirk-n@dircon.co.uk
Subject: Re: [INTERFACES] timeouts in libpq- can libpq requests block forever/a very long time?
In-Reply-To: <8248.938889802@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox