From: Tino Wildenhain <tino@wildenhain.de>
To: Kranti™ K K Parisa <kranti.parisa@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: [PERFORM] Very Urgent : Sequences Problem
Date: Wed, 19 Nov 2008 17:31:22 +0100
Message-ID: <49243F5A.1020300@wildenhain.de> (raw)
In-Reply-To: <4478b4ac0811190754n42d9539v4bd42350fac24d1@mail.gmail.com>
References: <4478b4ac0811190754n42d9539v4bd42350fac24d1@mail.gmail.com>
Hi,
Kranti™ K K Parisa wrote:
> Hi,
>
> I have defined sequence on a table something like this
>
>
> CREATE SEQUENCE items_unqid_seq
> INCREMENT 1
> MINVALUE 0
> MAXVALUE 9223372036854775807
> START 7659
> CACHE 1;
>
> this is on a table called items. where i have currently the max(unq_id)
> as 7659.
>
> and in the stored procedure when i am inserting values into the items
> table for the unq_id column i am using the sequence as follows:
>
> nextval('items_unqid_seq'::text)
>
>
> it seems to be working some times. and the sequences are not getting
> updated sometime. which is casuing primary key exceptions.
Thats actually not possible. Sequences are never rolled
back. The only way would be using stale values from
your function call or some other inserts trying to
overwrite or insert into the table twice with the same
id.
> please advise as soon as possible.
>
> is there any trivial problem with sequences in postgresql??
nope.
> thanks in advance.
This is neither admin nor performance related so you better
send such questions to psql-general.
Thank you
Tino
Attachments:
smime.p7s (application/x-pkcs7-signature, 3.2K) download
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: tino@wildenhain.de, kranti.parisa@gmail.com, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] Very Urgent : Sequences Problem
In-Reply-To: <49243F5A.1020300@wildenhain.de>
* 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