| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: interesting side effect of autocommit = off |
| Date: | 2002-10-15 02:00:46 |
| Message-ID: | 3DAB76CE.2030205@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Denis A Ustimenko | 2002-10-15 03:30:01 | Re: droped out precise time calculations in src/interfaces/libpq/fe-connect.c |
| Previous Message | Steven Singer | 2002-10-15 01:42:15 | Re: Triggers and Schema's. |