| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Barry Lind <barry(at)xythos(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: experiences with autocommit functionality in 7.3 |
| Date: | 2002-10-13 14:51:44 |
| Message-ID: | 28735.1034520704@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Barry Lind <barry(at)xythos(dot)com> writes:
> Below is the current behavior (based on a fresh pull from cvs this morning):
> Current State Action End State
> ACon and NIT set ACon ACon and NIT
> set ACoff ACoff and IT*
Bruce was supposed to fix this. We agreed that a SET command would
never initiate a transaction block on its own. Looks like it's not
there yet --- but IMHO the behavior should be
ACon and NIT set ACon ACon and NIT
set ACoff ACoff and NIT
ACon and IT set ACon ACon and IT
set ACoff ACoff and IT*
ACon and IT* set ACon ACon and IT*
set ACoff ACoff and IT
ACoff and NIT set ACon ACon and NIT
set ACoff ACoff and NIT
ACoff and IT set ACon ACon and IT*
set ACoff ACoff and IT
ACoff and IT* set ACon ACon and IT
set ACoff ACoff and IT*
Will that resolve your concern?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-13 14:55:44 | Re: mac typo prob? |
| Previous Message | Patrick Welche | 2002-10-13 13:16:09 | mac typo prob? |