From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | J C Lawrence <claw(at)kanga(dot)nu> |
Cc: | patrick keshishian <patrick(at)pioneerdigital(dot)com>, Charles Tassell <ctassell(at)isn(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: COMMIT after an ERROR? |
Date: | 2001-10-13 14:13:25 |
Message-ID: | Pine.BSF.4.21.0110130709200.4131-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 13 Oct 2001, J C Lawrence wrote:
> On Fri, 12 Oct 2001 19:35:30 -0700
> patrick keshishian <patrick(at)pioneerdigital(dot)com> wrote:
>
> > The only things that are not rolled back are advancing of
> > sequences and such. I suspect serial types also exhibit similar
> > behavior to sequences.
>
> Ahh, that's actually critical information (which makes sense too
> BTW). <thinks> Excellent. Then as long as the auto-ROLLBACK on
> error is a guaranteed ANSI behaviour rather than a PGSQL thing,
> everything is just perfect. Thanks.
Well, that's difficult. The spec is very hard to understand about
that. I believe we determined that our behavior was very very close to
complient, but that it does not match the standard reading of that
section. IIRC, usually only the statement rolls back unless its a commit
that failed (which causes the transaction to roll back entirely), but
there's a clause for a class of errors which cause the transaction to
rollback entirely which is not defined and postgres treats any error
as falling into that category.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-10-13 14:54:19 | Re: Any Good Way To Do Sync DB's? |
Previous Message | David Pirotte | 2001-10-13 14:03:12 | why do I receive these news-group posts ? |