From: Bruce Momjian Date: Sun, 25 Sep 2005 03:06:41 +0000 (+0000) Subject: Document why PQtrace and ecpg debug() can crash the application if the X-Git-Tag: REL8_1_0BETA3~110 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ccc0a1326ed5c8ba7aa3338cfa7d5e1b9693032b;p=postgresql Document why PQtrace and ecpg debug() can crash the application if the DLL compiles to not match the application. --- diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 4364ff0fce..8e6168cbdb 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -1,5 +1,5 @@ @@ -1607,6 +1607,13 @@ ECPG = ecpg useful when searching for errors in your SQL statements. + + + On Win32, if the ecpg libraries and application are compiled with + different flags, this function call will crash the application because the + internal representation of the FILE pointers differ. + + diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 7f9bc97b0d..c788386f6a 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ @@ -3515,6 +3515,13 @@ affect the messages available from already-existing void PQtrace(PGconn *conn, FILE *stream); + + +On Win32, if the libpq library and application are compiled with +different flags, this function call will crash the application because the +internal representation of the FILE pointers differ. + +