| From: | Sean Chittenden <sean(at)chittenden(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New SET/autocommit problem |
| Date: | 2002-10-22 17:10:46 |
| Message-ID: | 20021022171046.GA87110@perrin.int.nxad.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > WARNING: COMMIT: no transaction in progress
>
> > I've got tons of these warnings in my logs... is there a programmatic
> > way of determining if the current session is in a transaction?
>
> Not at present: you have to track it for yourself. One of the
> suggestions on the list for the next frontend/backend protocol revision
> (probably in 7.4) is to add a way for the backend to signal its
> transaction state: no transaction, in transaction, or in failed
> transaction seems like the set of possible states.
That would be fabulous because with autocommit set to off, the
complexity for tracking that in application is getting pretty
gnarly. -sc
--
Sean Chittenden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-22 17:15:05 | Re: pg_dump and large files - is this a problem? |
| Previous Message | Bruce Momjian | 2002-10-22 17:10:21 | Re: One 7.3 item left |