On 07/10/04:27/6, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > (We could talk about exception support in plpgsql or other language
> > handlers but I don't think this is going to happen for 7.5.)
>
> Au contraire ... I think it *must* happen, and indeed that
> subtransaction su
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> (We could talk about exception support in plpgsql or other language
> handlers but I don't think this is going to happen for 7.5.)
Au contraire ... I think it *must* happen, and indeed that
subtransaction support in plpgsql is not different from excepti
> Some sort of modification will be needed to the error processing
> mechanism, but this is beyond me at this point ... I don't have any
> idea how could this be.
So.. If you cannot rollback a subtransaction within a plpgsql function
(all function types or just that one?) then there is no point i
On Thu, Jul 08, 2004 at 04:52:04PM -0400, Rod Taylor wrote:
> > create function crashme2() returns int strict language plpgsql as '
> > begin
> >subbegin;
> > select foo; -- aborts the transaction
> > -- did not close the subxact
> > end;';
>
> I'm not s
> create function crashme2() returns int strict language plpgsql as '
> begin
>subbegin;
> select foo; -- aborts the transaction
> -- did not close the subxact
> end;';
I'm not sure I follow. Are you saying that the following code or
something similar wi
