Re: High CPU shoot during poll retry
| От | Gaurav Srivastava |
|---|---|
| Тема | Re: High CPU shoot during poll retry |
| Дата | |
| Msg-id | CAAXqS3BwUYinj28xm-y1FkJaafJC-1J4ksf808KQK0wUh8AQTw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: High CPU shoot during poll retry (Heikki Linnakangas <hlinnakangas@vmware.com>) |
| Список | pgsql-odbc |
Hi Heikki,
Yes i understand it would be difficult but i would like to develop this patch as it would create huge flexibility in psqlODBC and help a lot to its users.Gaurav Srivastava | Associate Consultant
GlobalLogic
P +91.120.4342000.2920 M +91.9953996631 S ta5ramn1
www.globallogic.com
http://www.globallogic.com/email_disclaimer.txt
GlobalLogic
P +91.120.4342000.2920 M +91.9953996631 S ta5ramn1
www.globallogic.com
http://www.globallogic.com/email_disclaimer.txt
On Wed, Dec 17, 2014 at 8:31 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
On 12/17/2014 04:01 PM, Gaurav Srivastava wrote:Hi Heikki,
Sincere thanks for your quick responses.
Can we have similar functionality added in psqlODBC as in unmodified code
when nowait==False it waits for "infinite duration" ,Instead If we have a
configured timed wait,anybody can configure it as per their requirement.
Yeah, that would be nice. The ODBC standard way to do it is to set the SQL_ATTR_QUERY_TIMEOUT attribute with SQLSetStmtAttr. It's not supported by the psqlodbc driver, however. It probably would be quite difficult to implement, but patches are welcome..
You could also do "set statement_timeout=2" to set a timeout in the server, but that wouldn't help with network problems.
- Heikki
В списке pgsql-odbc по дате отправления: