Re: error handling unique key constraint in pgsql

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: Dinesh <dbhandary(at)mongonet(dot)net>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: error handling unique key constraint in pgsql
Date: 2008-06-10 19:09:52
Message-ID: dcc563d10806101209x4edfd77dl28bf514a0742d845@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Jun 10, 2008 at 10:52 AM, Dinesh <dbhandary(at)mongonet(dot)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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2008-06-10 19:49:16 Re: what happend to my database
Previous Message Alvaro Herrera 2008-06-10 17:09:11 Re: Cannot Drop Schema