Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function. - Mailing list pgsql-odbc
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.
Best Regards,
rohtodeveloper
Date: Mon, 20 Oct 2014 21:06:24 +0900
Subject: Re: [ODBC] This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.
From: michael.paquier@gmail.com
To: rohtodeveloper@outlook.com
CC: pgsql-odbc@postgresql.org
On Mon, Oct 20, 2014 at 8:56 PM, rohtodeveloper <rohtodeveloper@outlook.com> wrote:
-- If I create a postgres's FUNCTION(myfunc()) using C language，and use this FUNCTION to call the odbc driver(psqlodbcw.so),this problem may happen.
Why would you want to do that? ODBC driver should run as a client process and should not need to interact in any way with a Postgres server process, aka an internal session of the instance.
Michael
pgsql-odbc by date: