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@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073
