| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Jaime Casanova" <systemguards(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: savepoint improvements |
| Date: | 2007-01-22 16:22:37 |
| Message-ID: | 1169482957.3776.349.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2007-01-22 at 16:11 +0000, Gregory Stark wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
>
> > BEGIN;
> > stmt1;
> > stmt2; <-- error
> > stmt3;
> > COMMIT;
> >
> > results in stmt3 completing successfully even though stmt1 and stmt2 do
> > not == broken script.
>
> stmt1 would still be completed successfully.
OK, understood. ON_ERROR_ROLLBACK is what we need, for psql only.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-01-22 17:06:00 | Re: savepoint improvements |
| Previous Message | Merlin Moncure | 2007-01-22 16:21:12 | Re: savepoint improvements |