| From: | Dang Minh Huong <kakalot49(at)gmail(dot)com> |
|---|---|
| To: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Degradation of performance when upgrade psqlodbc to 09.03.0400 |
| Date: | 2016-02-16 03:40:24 |
| Message-ID: | 8588FA7D-74ED-4CD9-9E35-672DD884625E@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi Inoue-san,
I have tested some commits in revision 09.03.0100 and found that your "revise MSDTC support" patch made SQLSetConnectAttr issue.
Can you simply explain how does your patch cause that issue?
Thanks and best regards,
bocap
> Hi Dang,
>
> I would examine it tomorrow.
>
> regards,
> Hiroshi Inoue
>
>> On 2016/02/15 18:12, Dang Minh Huong wrote:
>> Hi Inoue-san, Heikki-san,
>>
>> Sorry for continuous disturbing you in this topic.
>>
>> We found the below SQLSetConnectAttr issue, which was solved in 09.05.
>> Follow the topic and we solved performance problem in 09.03.0340 by do SQLSetConnectAttr after create connection.
>>
>> http://postgresql.nabble.com/issue-SQLDriverConnect-will-clear-existing-connect-attribute-setting-td5832902.html#a5836129
>>
>> As my confirmation, SQLSetConnectAttr issue is started from 09.03.0100. Which your "Revise MSDTC support" patch is applied.
>> Does your patch is related to SQLSetConnectAttr issue above?
>> If yes, how it does ?
>> # Sorry but i just want to know the root cause.
>>
>> Thanks and best regards,
>> bocap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-16 04:15:58 | Re: [BUGS] BUG #13956: ODBC driver has a memory leak with TIMESTAMP(0) |
| Previous Message | Adrian Klaver | 2016-02-15 20:24:20 | Re: PostgreSQL: Autocommit through windows odbc driver doesnt work!!! |