From: Robins <tharakan@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Locking vs. Exceptions
Date: Thu, 2 Nov 2006 18:15:53 +0530
Message-ID: <36af4bed0611020445s445e3fe8o344f529190a8dfea@mail.gmail.com> (raw)
Hi,
The documentation says that function blocks with exceptions are far costlier
than without one.
So if I need to implement an INSTEAD OF trigger (after checking for unique
constraint violations) which way should I go ?
1. Get a table lock
2. Use 'Select ... For Update' (which could be used to lock only the desired
recordsets)
3. Use Exceptions
Any advice / experiences or even pointers would be helpful.
Thanks
Robins Tharakan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tharakan@gmail.com
Subject: Re: Locking vs. Exceptions
In-Reply-To: <36af4bed0611020445s445e3fe8o344f529190a8dfea@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox