Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.
От | Inoue, Hiroshi |
---|---|
Тема | Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function. |
Дата | |
Msg-id | 54505FE6.4060704@tpf.co.jp обсуждение исходный текст |
Ответ на | Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function. (rohtodeveloper <rohtodeveloper@outlook.com>) |
Ответы |
Re: This may be a bug: odbc's function"check_client_encoding"
have the same name with postgres's function.
|
Список | pgsql-odbc |
(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? regards, Hiroshi Inoue -- I am using the free version of SPAMfighter. SPAMfighter has removed 12846 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
В списке pgsql-odbc по дате отправления: