From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dirk Niggemann <dirk-n(at)dircon(dot)co(dot)uk> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] timeouts in libpq- can libpq requests block forever/a very long time? |
Date: | 1999-10-02 18:43:22 |
Message-ID: | 8248.938889802@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Dirk Niggemann <dirk-n(at)dircon(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | John Cusick | 1999-10-03 00:49:57 | Re: [INTERFACES] PL_na undeclared |
Previous Message | Dirk Niggemann | 1999-10-02 18:14:00 | timeouts in libpq- can libpq requests block forever/a very long time? |