From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | "Itnal, Prakash (NSN - IN/Bangalore)" <prakash(dot)itnal(at)nsn(dot)com> |
Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Issue with retry_count in socket.c and fix for the same |
Date: | 2014-05-27 14:26:56 |
Message-ID: | 5384A0B0.9020906@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 05/15/2014 02:25 PM, Heikki Linnakangas wrote:
> I wonder why we need any timeout or retry counters, ever. Frankly, I'm
> inclined to just rip all that out. A timeout would be a useful feature
> for many applications, to detect a broken connection more quickly, but
> the way it's currently implemented is pretty much useless for that. For
> starters, it would have to be configurable, because many applications
> would not want to have a timeout at all. A built-in timeout of 60
> seconds or so, which I think you'd get with your patch, would be too
> short for OLAP kind of queries that can run for hours before returning
> any results.
Ok, I removed the broken logic, for the sake of cleaning up the code. It
still won't give the kind of a timeout that you hoped for, but at least
it's less bogus now.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-05-27 14:34:33 | Re: Issue with retry_count in socket.c and fix for the same |
Previous Message | Michael Paquier | 2014-05-27 14:14:58 | Re: [ANNOUNCE] psqlODBC 09.03.0300 Released |