| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Swan <tswan(at)idigx(dot)com> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, 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 17:35:27 |
| Message-ID: | 200307221735.h6MHZRL03006@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Swan wrote:
> >>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...
> >
> >
> I was just about to mention that one. Perhaps a ROLLBACK ALL would be
> of benefit to allow a clean state and start to work again.
>
> Doesn't autocommit behavior affect this as well?
No, autocommit is now in the clients, but even if it was in the server,
BEGIN;COMMIT would be OK.
--
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 | Bruno Wolff III | 2003-07-22 17:43:58 | Re: suggestions to improve postgresql suitability for data-mining |
| Previous Message | Andreas Pflug | 2003-07-22 17:30:05 | initdb fails: problem with array? |