Re: interesting side effect of autocommit = off
Joe Conway <mail@joeconway.com>
From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Barry Lind <barry@xythos.com>, pgsql-hackers@postgresql.org
Date: 2002-10-15T02:00:46Z
Lists: pgsql-hackers
Tom Lane wrote: > Yeah, and libpq does one too in some cases :-(. Both of these need to > be fixed before 7.3 if possible. > > Whether we fix these or not, it'd be a good idea to document that > turning autocommit off in postgresql.conf is not yet well-supported. > I doubt that all client-side code will be happy with that for awhile > yet ... Yup -- here's another example. I was playing around with autocommit off in postgresql.conf to see the effect on dblink. Just now I tried to use pg_dumpall in preparation for an initdb, and got this: $ pg_dumpall > cur.2002.10.14.dmp pg_dump: WARNING: BEGIN: already a transaction in progress pg_dump: could not set transaction isolation level to serializable: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query pg_dumpall: pg_dump failed on dblink_test_master, exiting Joe