Обсуждение: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.
I found a problem in the odbc driver on linux platfrom.
Inside the odbc driver,there is a function called check_client_encoding() ,however,there is also a function which has the same name inside the postgres.
once the two functions are in the same process, problems may occur,because the system may choose the wrong function to execute.
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.
The follow picture explain the situation.
The declaration of the two functions are as follows:
➀ UCHAR *check_client_encoding(const UCHAR *sql_string);
② bool check_client_encoding(char **newval, void **extra, GucSource source);
I want to call the odbc's function "check_client_encoding",however it calls the postgres's function "check_client_encoding".
I think this probably is a bug.
Call you help me with this problem?
Thank you so much!
Вложения
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.
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
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.
Michael
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,
From: rohtodeveloper@outlook.com
To: michael.paquier@gmail.com
CC: pgsql-odbc@postgresql.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.
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
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.
Michael