| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Marcus Börger <marcus(dot)boerger(at)post(dot)rwth-aachen(dot)de>, ivan <iv(at)psycho(dot)pl>, Joe Conway <mail(at)joeconway(dot)com>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: php with postgres |
| Date: | 2003-07-22 16:35:48 |
| Message-ID: | 200307221635.h6MGZmP25897@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
scott.marlowe wrote:
> > > It does generate the usual error if the current transaction block is in
> > > ABORT state. So the correct querystring to send would be something like
> > >
> > > "ROLLBACK; RESET ALL"
> >
> > Oh, I remember that now as part of the persistent connection code. As I
> > remember, we told them to do BEGIN;COMMIT; to clear any open transaction
> > state passed to the new client. Is that in there? If not, it has to be
> > added too. ROLLBACK will generate an error if you are not in a
> > transaction, so it would fill the logs with errors.
>
> Won't that break when we have nested transactions implemented? i.e.
> begin;commit; would just open a sub transaction and have no effect on the
> outer transaction...
Yes, it would break. I am not sure how we are going to flag that we
want to rollback all nested transactions, maybe ROLLBACK ALL.
--
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 | Bruce Momjian | 2003-07-22 16:39:10 | Re: Thread-safe questions in configure |
| Previous Message | Josh Berkus | 2003-07-22 16:28:36 | Re: dblink_ora - a first shot on Oracle ... |