Re: [patch] fix buffer overrun in logging, and code cleanup

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: [patch] fix buffer overrun in logging, and code cleanup
Date: 2016-05-30 01:13:17
Message-ID: 0A3221C70F24FB45833433255569204D1F57B994@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> From: Inoue, Hiroshi [mailto:h-inoue(at)dream(dot)email(dot)ne(dot)jp]
> However forcelog() exists in msdtc_enlist.cpp at first glance.

Oh, I overlooked it. I removed the use of forcelog() there by:

1) Remove #ifdef _LOCK_DEBUG ... #endif code fragments.
2) Replace remaining forcelog() call sites with mylog(). I think mylog() should be used to allow users of the log file accumulation.

Regards
Takayuki Tsunakawa

Attachment Content-Type Size
mylog_cleanup_v2.patch application/octet-stream 9.4 KB

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2016-05-30 01:24:16 Re: ADO CommandTimeout vs Postgres statement_timeout parameter
Previous Message Adrian Klaver 2016-05-27 19:45:56 Re: ODBC connections