From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Commit turns into rollback? |
Date: | 2006-03-17 13:22:56 |
Message-ID: | 1142601776.3819.7.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ühel kenal päeval, R, 2006-03-17 kell 14:10, kirjutas Peter Eisentraut:
> Am Freitag, 17. März 2006 13:03 schrieb Hannu Krosing:
> > > If I send a COMMIT, I want a commit to happen or an error.
> >
> > You already got several errors.
>
> Right, but a defensively programmed application, I want to get all the errors
> all the time at every possible place.
>
> > Or would you like a mode where you need explicitly send a ROLLBACK to
> > get out ?
>
> I faintly recall that this used to be the behavior.
in 7.4 it was worse
ahf=# begin;
BEGIN
ahf=# select 1/0;
ERROR: division by zero
ahf=# commit;
COMMIT
it still did a rollback, but reported a COMMIT
-----------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-17 14:46:16 | Re: Automatically setting work_mem |
Previous Message | Peter Eisentraut | 2006-03-17 13:10:40 | Re: Commit turns into rollback? |