DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=IkkzrtubvKxdN9cSc8SmR6oHJjiVpsuVxYwC8QffD6bYFVW8TsUvYrj1Ca7sF8ghsI
	bunCVR8C6Wo9hOn2UFHl1eA+1lbjqk4kq9sp2X6G6LdxfNeWJW7D5ieRJrdxlu8Sk+xq
	RbZiU/M8rP+xaADl7vOnKb4gW63Zn+Uk2dfuo=
Message-ID: <dcc563d10806101209x4edfd77dl28bf514a0742d845@mail.gmail.com>
Date: Tue, 10 Jun 2008 13:09:52 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: Dinesh <dbhandary@mongonet.net>
Subject: Re: error handling unique key constraint in pgsql
Cc: pgsql-admin@postgresql.org
In-Reply-To: <484EB14B.4010003@mongonet.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <484EB14B.4010003@mongonet.net>

On Tue, Jun 10, 2008 at 10:52 AM, Dinesh <dbhandary@mongonet.net> wrote:
> Hi All,
>
> I was wondering if there is an easy way to handle unique key constraint in
> pgsql. Right now my entire transaction aborts if it tries to insert
> duplicate keys, but I would like to handle this
> scenario in such a way that the transaction will not break.
>
> Please let me know if you have done something like this. I greatly
> appreciate your help.

There are a couple of approaches:

process the inserts in a pl/pgsql function  and use the exception
handling in there to catch them.

Use savepoints.

Both of these use the same underlying mechanisms, and both tend to be
expensive in terms of overhead.