| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
| Cc: | "Olleg Samojlov" <olleg(at)jane(dot)telecom(dot)mipt(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Changing behavior of BEGIN...sleep...do something...COMMIT |
| Date: | 2003-04-04 14:25:13 |
| Message-ID: | 5400.1049466313@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> Somehow I did not see that conclusion made.
> I thought, at least for JDBC, it is already successfully used ?
Barry, at least, seemed to be happy with removing it, given the planned
protocol change to report current transaction state after every query.
> I think the backend autocommit is useful. Maybe only the
> installation/database/user wide GUC setting should be depricated/
> disabled, so it is only used by a session SET ?
That wouldn't really solve any of the problems.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-04-04 14:37:45 | Re: Changing behavior of BEGIN...sleep...do something...COMMIT |
| Previous Message | Jeffrey D. Brower | 2003-04-04 12:45:29 | Re: [HACKERS] OSS database needed for testing |