Using git bisect, where "good" is defined as not crashing the PostgreSQL server nor causing a gpf in the client program, and "bad" does one or the other): Last "good" commit: http://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=3cf4dedfbb435f653785a967e951956046f0a8cb <http://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=3cf4dedfbb435f653785a967e951956046f0a8cb> The commit right after that actually crashes the PostgreSQL 9.2.4 server--I don't get a chance to get a gpf at the client when running my test: (this is in the server log) 2013-04-22 15:47:04 EDT LOG server process (PID 13732) was terminated by exception 0xC0000005 First "bad" commit: http://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=6e45dcb08093d81f244ad6321cbd529d0a7efe61 <http://git.postgresql.org/gitweb/?p=psqlodbc.git;a=commit;h=6e45dcb08093d81f244ad6321cbd529d0a7efe61> Note that this "bad" commit requires 09.00 headers to compile (though version is still at 08.04), otherwise get two unresolved externals: loadlib.obj : error LNK2019: unresolved external symbol _PQescapeLiteral referenced in function _connect_with_param_available loadlib.obj : error LNK2019: unresolved external symbol _PQconnectdbParams referenced in function _CALL_PQconnectdbParams .\Release\psqlodbc35w.dll : fatal error LNK1120: 2 unresolved externals Apparently those two symbols were introduced in the 09.00 code stream. Thanks...jack -- View this message in context: http://postgresql.1045698.n5.nabble.com/UseDeclareFetch-1-Fetch-100-UseServerSidePrepare-0-causes-Windows-gpf-in-Unicode-Driver-versions-08-0-tp5752790p5752937.html Sent from the PostgreSQL - odbc mailing list archive at Nabble.com.
pgsql-odbc by date:
Соглашаюсь с условиями обработки персональных данных
