Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.

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.

Best Regards,
rohtodeveloper
From: rohtodeveloper(at)outlook(dot)com
To: michael(dot)paquier(at)gmail(dot)com
CC: pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.
Date: Tue, 28 Oct 2014 17:35:48 +0000

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(dot)paquier(at)gmail(dot)com
To: rohtodeveloper(at)outlook(dot)com
CC: pgsql-odbc(at)postgresql(dot)org

On Mon, Oct 20, 2014 at 8:56 PM, rohtodeveloper <rohtodeveloper(at)outlook(dot)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