Index: doc/src/sgml/ecpg.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v retrieving revision 1.33 diff -c -r1.33 ecpg.sgml *** doc/src/sgml/ecpg.sgml 2002/01/07 02:29:11 1.33 --- doc/src/sgml/ecpg.sgml 2002/01/18 20:30:13 *************** *** 1053,1066 **** ! All SQL statements are performed in one ! transaction unless you issue a commit transaction. To accomplish ! this auto-transaction behavior, the first statement and the first ! statement after a commit or rollback always begins a new transaction. To ! disable this feature, use the command-line ! option. - --- 1053,1068 ---- ! In the default mode, queries are committed only when exec ! sql commit is issued. Ecpg ! also supports auto-commit of transactions via the ! command-line option or via the exec ! sql set autocommit to on statement. In ! autocommit mode, each query is automatically ! committed unless it is inside an explicit transaction block. This ! mode can be explicitly turned off using exec sql set ! autocommit to off. Index: doc/src/sgml/libpq.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v retrieving revision 1.85 diff -c -r1.85 libpq.sgml *** doc/src/sgml/libpq.sgml 2002/01/07 02:29:12 1.85 --- doc/src/sgml/libpq.sgml 2002/01/18 20:30:19 *************** *** 2109,2118 **** libpq is thread-safe as of PostgreSQL 7.0, so long as no two threads ! attempt to manipulate the same PGconn object at the same time. In particular, ! you cannot issue concurrent queries from different threads through the same ! connection object. (If you need to run concurrent queries, start up multiple ! connections.) --- 2109,2125 ---- libpq is thread-safe as of PostgreSQL 7.0, so long as no two threads ! attempt to manipulate the same PGconn object at the same ! time. In particular, you cannot issue concurrent queries from different ! threads through the same connection object. (If you need to run ! concurrent queries, start up multiple connections.) ! ! ! However, libpq clients using the ! crypt encryption method rely on the ! crypt() operating system function, which often is not ! thread-safe. It is better to use MD5 encryption, ! which is guarantted to be thread-safe on all platforms. Index: doc/src/sgml/ref/ecpg-ref.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v retrieving revision 1.16 diff -c -r1.16 ecpg-ref.sgml *** doc/src/sgml/ref/ecpg-ref.sgml 2002/01/06 18:12:00 1.16 --- doc/src/sgml/ref/ecpg-ref.sgml 2002/01/18 20:30:20 *************** *** 57,63 **** -t ! Turn on auto-commit of transactions. --- 57,66 ---- -t ! Turn on auto-commit of transactions. In this mode, each query is ! automatically committed unless it is inside an explicit ! transaction block. In the default mode, queries are committed ! only when exec sql commit is issued. *************** *** 403,434 **** See the TODO file in the source for some more missing features. - - --- 406,411 ----