Re: Transaction Handling in pl/pgsql - Mailing list pgsql-general

From Craig Bryden
Subject Re: Transaction Handling in pl/pgsql
Date
Msg-id 002701c58713$34367640$0200a8c0@amd2800
Whole thread Raw
In response to Transaction Handling in pl/pgsql  ("Craig Bryden" <postgresql@bryden.co.za>)
List pgsql-general
Thanks a stack. That has answered by question.

Craig


----- Original Message -----
From: "Douglas McNaught" <doug@mcnaught.org>
To: "Craig Bryden" <postgresql@bryden.co.za>
Cc: "pgsql" <pgsql-general@postgresql.org>
Sent: Tuesday, July 12, 2005 8:46 PM
Subject: Re: [GENERAL] Transaction Handling in pl/pgsql


> "Craig Bryden" <postgresql@bryden.co.za> writes:
>
> > OK. I have read that. The part that sticks out is "A block containing an
> > EXCEPTION clause is significantly more expensive to enter and exit than
a
> > block without one. Therefore, don't use EXCEPTION without need. ".
> > Performance is paramount to me.
> >
> > If I ommit the EXCEPTION clause will all the statements still be rolled
back
> > if an error occurs?
>
> Yes, if you don't use EXCEPTION clauses the behavior is the same as
> previous versions.
>
> -Doug
>
>


pgsql-general by date:

Previous
From: Douglas McNaught
Date:
Subject: Re: Transaction Handling in pl/pgsql
Next
From: Tom Lane
Date:
Subject: Re: FW: index bloat