Thanks very much.
We decide to use your solution1(20141029_pgodbc_rename_check_encoding.patch).
On the other hand, by the way, which solution does the community prefer to choose?
regards,
rohtodeveloper
--- 原始邮件 ---
发件人： "Inoue, Hiroshi" <inoue@tpf.co.jp>
已发： 2014年10月30日 上午11:00
收件人： "rohtodeveloper" <rohtodeveloper@outlook.com>
抄送： "Michael Paquier" <michael.paquier@gmail.com>, pgsql-odbc@postgresql.org
主题： Re: [ODBC] This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.
(2014/10/29 18:02), Inoue, Hiroshi wrote:
> (2014/10/29 12:32), Inoue, Hiroshi wrote:
>> (2014/10/29 2:49), rohtodeveloper wrote:
>>> I'm so sorry, it seems that there was something wrong with the pictures
>>> in my last letter.
>>> Here I send the mail again with the correct pictures:
>>>
>>> Thanks a lot for your answer.
>>>
>>> Well ,in fact, if I use the extension called odbc_fdw , the same problem
>>> will happen.
>>>
>>> That’s because the odbc_fdw will also call the odbc driver.
>>>
>>> The follow pictures explain the situation.
>>>
>>> When use the odbc_fdw extension, the libraries are loaded in the
>>> following way.
>>>
>>> After all the libraries are loaded, When the function
>>> check_client_encoding is called , the whole postgres process will crash
>>> , result in a core dumped problem.
>>
>> Which check_client_encoding() call causes the crash?
>
> Oops I missed your anothe post.
> OK check_client_encoding() in the driver causes the crash.
> Currently all global symbols in the driver are exported.
> Exporting only ODBC APIs may solve the problem.
Possibly attached patch for Makefile.am fixes the problem.
Autoreconf, configure, make and make install are needed.
Could you try it?
regards,
Hiroshi Inoue
--
I am using the free version of SPAMfighter.
SPAMfighter has removed 12852 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len
Do you have a slow PC? Try a Free scan
http://www.spamfighter.com/SLOW-PCfighter?cid=sigen
