Date: Mon, 31 Mar 2008 20:52:35 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Ravi Chemudugunta <chemuduguntar@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Implications of Using Exceptions
Message-ID: <20080401005235.GM4999@tamriel.snowman.net>
Mail-Followup-To: Ravi Chemudugunta <chemuduguntar@gmail.com>,
	pgsql-performance@postgresql.org
References: <7a4208ef0803311720s1dac8362gff2477d3dc534968@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="XRwESHC7KXlqFpSs"
Content-Disposition: inline
In-Reply-To: <7a4208ef0803311720s1dac8362gff2477d3dc534968@mail.gmail.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)


--XRwESHC7KXlqFpSs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Ravi Chemudugunta (chemuduguntar@gmail.com) wrote:
> Which version is faster?

In general I would recommend that you benchmark them using
as-close-to-real load as possible again as-real-as-possible data.

> Does the exception mechanism add any overhead?

Yes, using exceptions adds a fair bit of overhead.  Quote from the
documentation found here:
http://www.postgresql.org/docs/8.3/static/plpgsql-control-structures.html

Tip:  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.

> Which is more cleaner?

That would be in the eye of the beholder, generally.  Given the lack of
complexity, I don't think 'cleanness' in this case really matters all
that much.

	Enjoy,

		Stephen

--XRwESHC7KXlqFpSs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH8YdTrzgMPqB3kigRAv2uAJwOED/o2a1SAxCYjf8PQdbQndt/OQCeMCUI
WpOiyc5Qi9fYu8kVjVvJxWk=
=mDi4
-----END PGP SIGNATURE-----

--XRwESHC7KXlqFpSs--