From 26993b2918551552b74b559ab410228dc0670cd5 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 30 Aug 2002 22:18:07 +0000 Subject: AUTOCOMMIT mode is now an available backend GUC variable; setting it to false provides more SQL-spec-compliant behavior than we had before. I am not sure that setting it false is actually a good idea yet; there is a lot of client-side code that will probably be broken by turning autocommit off. But it's a start. Loosely based on a patch by David Van Wie. --- doc/src/sgml/release.sgml | 3 ++- doc/src/sgml/runtime.sgml | 25 ++++++++++++++++++++++++- 2 files changed, 26 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 78606b68e94..3ba21bc1ab7 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -24,6 +24,7 @@ CDATA means the content is "SGML-free", so you can write without worries about funny characters. --> @@ -1135,6 +1135,29 @@ env PGOPTIONS='-c geqo=off' psql + + AUTOCOMMIT (bool) + autocommit + + + If set to true, PostgreSQL will + automatically do a COMMIT after each successful command + that is not inside an explicit transaction block (that is, unless a + BEGIN with no matching COMMIT has been + given). + If set to false, PostgreSQL will commit + the effects of commands only on receiving an explicit + COMMIT command. This mode can also be thought of as + implicitly issuing BEGIN whenever a command is received + and PostgreSQL is not already inside + a transaction block. + The default is true, for compatibility with historical + PostgreSQL behavior. But for maximum + compatibility with the SQL specification, set it to false. + + + + AUSTRALIAN_TIMEZONES (bool) Australian time zones -- cgit v1.2.3