From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
Cc: | Sean Chittenden <sean(at)chittenden(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: SET autocommit begins transaction? |
Date: | 2002-09-18 23:17:08 |
Message-ID: | 200209182317.g8INH8V08325@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thomas Lockhart wrote:
> ...
> > I think if we special case autocommit we have to force it to start a
> > transaction.
>
> Be aware that "SET AUTOCOMMIT" does *not* start a transaction in other
> systems (at least in Ingres, where I first ran into the feature).
>
> This case is illustrating a general issue with trying to bracket
> variables within transactions; the "special case" is that if a
> transaction is not open then the change should be global across
> transactions.
>
> Any counterexamples would argue for two separate behaviors, not for
> shoehorning everything into one, uh, shoe.
I am fine with special casing autocommit. Is that what you are
suggesting?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2002-09-18 23:22:11 | Re: SET autocommit begins transaction? |
Previous Message | Bruce Momjian | 2002-09-18 23:14:20 | Re: SET autocommit begins transaction? |