Re: Rollback on Error

From: "Michael Paesold" <mpaesold(at)gmx(dot)at>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Rollback on Error
Date: 2004-09-14 10:11:10
Message-ID: 005301c49a43$2a6eb040$ad01a8c0@zaphod
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Peter Eisentraut wrote:

> Michael Paesold wrote:
> > I though the postgres behaviour of rolling back the whole transaction
> > was standard?
>
> No.

Thanks for putting that straigt.

> > If that is not the case, I don't understand why core
> > seems to be against a mode (GUC), where an implicit savepoint is
> > generated before each statement so that "rollback of the last
> > statement" would be possible.
>
> Because it's dangerous in noninteractive mode. When you send a
> transaction to the server, you don't want some statements be left out.

I understand it's dangerous, it would possibly introduce data-inconsistency
in all applications that don't check for errors after each statement...

Still it would be very useful in interactive psql...
of course, it's bad in scripted mode. Perhaps it could be implemented inside
psql? Would such a patch be accepted?

Regards,
Michael Paesold

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Csaba Nagy 2004-09-14 10:13:20 Re: Rollback on Error
Previous Message Klint Gore 2004-09-14 10:04:10 logging rule execution?

Browse pgsql-hackers by date

  From Date Subject
Next Message Csaba Nagy 2004-09-14 10:13:20 Re: Rollback on Error
Previous Message Peter Eisentraut 2004-09-14 09:56:42 Re: Rollback on Error