From: Benjamin Krajmalnik <kraj@illumen.com>
To: pgsql-admin@postgresql.org
Subject: Error inserting row on unique key
Date: Thu, 20 Apr 2006 11:31:14 -0600
Message-ID: <8511B4970E0D124898E973DF496F9B4325157D@stash.stackdump.local> (raw)
I have a large table which uses a sequence for column which is defined as the primary key.
Our systems is a real time data acquisition system, so we have "insert" statements going through it wrapped inside stored procedure.
Every once in a while I get an inserio error on a violation of a unique constraint on the primary key.
Could this be caused by a subsequent call to the stored procedure which took place before the sequence on the prior stored procedure fired?
If so, do you recommend taking the call to the sequence out of the columns constraint definition and manually calling it as the firs step in the SP call?
As I said, this does not happen very often, but I have seen it happen.
Regards,
Benjamin
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kraj@illumen.com
Subject: Re: Error inserting row on unique key
In-Reply-To: <8511B4970E0D124898E973DF496F9B4325157D@stash.stackdump.local>
References: <8511B4970E0D124898E973DF496F9B4325157D@stash.stackdump.local>
* 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