Re: Getting "duplicate key value violates unique constraint" on 2nd run of function.

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: David Kerr <dmk(at)mr-paradox(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Getting "duplicate key value violates unique constraint" on 2nd run of function.
Date: 2009-11-25 23:49:02
Message-ID: dcc563d10911251549g6e659ee2idd7feca917a7177b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 25, 2009 at 3:19 PM, David Kerr <dmk(at)mr-paradox(dot)net> wrote:
> Howdy all.
>
> I've got a function that basically does this:
>
> DELETE FROM test where id = $1
> INSERT into test (id) values ($1);

You're missing a semi-colon up there, is that a problem?

> id is the primay key, so it has to be unique.
>
> First time I run it, works great.
> If I run it again in the same session, I get
> ERROR:  duplicate key value violates unique constraint "test_pkey"
>
> If I log out and then log back in, it runs fine again (the first time).
>
> Is there some setting for the function that I need to set to make this run correctly
> every time?

This should just work. Please post a more complete example of what's
happening (php code, queries something) that reproduces this problem
in a way I can just type it in and see it on my end.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-11-25 23:51:46 Re: Postgres database performance on 6 core Opteron vs 4 core Xeon
Previous Message Devrim GÜNDÜZ 2009-11-25 23:43:02 Re: pg_standby instructions