Performance of plpgsql with exception handlers

From: "Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com>
To: <pgsql-novice(at)postgresql(dot)org>
Subject: Performance of plpgsql with exception handlers
Date: 2005-06-01 22:34:27
Message-ID: 4A59B6AA01F1874283EA66C976ED51FC0E1A6B@COENGEXCMB01.cable.comcast.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

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

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2005-06-02 06:19:17 Re: Performance of plpgsql with exception handlers
Previous Message David Launen 2005-06-01 22:26:19 Enabling WAL with Postgres 8.0 for Windows