|
Home > Archive > PostgreSQL Newbies > June 2005 > Performance of plpgsql with exception handlers
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Performance of plpgsql with exception handlers
|
|
| Walker, Jed S 2005-06-01, 8:24 pm |
| The documentation states "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."
Our application developers would like to get back a simple code ( a
number) for any error that indicates what it is, and possibly a message.
So, as we would with Oracle we wanted to code in exception handlers to
do this, but the documenation has us concerned. Is putting exception
handlers into the pgsql code really a big performance hit?
Thanks,
Jed S. Walker
| |
| Tom Lane 2005-06-02, 3:23 am |
| "Walker, Jed S" <Jed_Walker@cable.comcast.com> writes:
> ... Is putting exception
> handlers into the pgsql code really a big performance hit?
Time it and see if it bothers you. The doc note is just there to let
people know that it isn't free; not to scare people away from using
it at all.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
|
|
|
|
|