| From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: savepoint improvements |
| Date: | 2007-01-21 17:40:17 |
| Message-ID: | c2d9e70e0701210940l753e389cnb56fa92d09b4705e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/21/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, 2007-01-19 at 15:12 -0500, Merlin Moncure wrote:
>
> > The missing piece of the puzzle is the ability to recover a failed
> > transaction without issuing a full commit/rollback.
>
> Agreed.
>
> I'd like to see a TODO item to allow an *option* to be set to choose
> between these two transactional behaviours.
[...]
> - continue on error i.e. COMMIT can/might succeed - though there are
> still cases where it cannot, such as a serializable exception.
>
and what should be the behaviour of that? the same as rollback?
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-21 17:54:17 | Re: Simplifying pg_am representation of index sortability |
| Previous Message | Simon Riggs | 2007-01-21 15:57:31 | Re: XML regression test failure |