From: | Arturo Perez <aperez(at)hayesinc(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problems with sequences |
Date: | 2006-09-07 01:31:33 |
Message-ID: | D46CA628-E48E-477C-81DB-376FB3368AF2@hayesinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sep 6, 2006, at 8:48 PM, Merlin Moncure wrote:
> On 9/6/06, Arturo Perez <aperez(at)hayesinc(dot)com> wrote:
>> What happens is that if I do a select nextval('seq') I get a number
>> that's lower than the
>> max primary key id. This is inspite of my doing
>> SELECT setval('seq', ((SELECT MAX(seq_ID) FROM table)+1))
>> ALTER SEQUENCE seq RESTART WITH <max + 1>;
>> select pg_catalog.setval(seq, <max+1>, true);
>>
>
> are you running those statements to fetch the next key in the table?
> you might have a race condition there. try wrappnig in a userlock.
>
> merlin
No, not running them to get the next key. Just trying to reset the
sequence so that I stop getting duplicates.
A race condition is unlikely as only one person can actually add
these things to the system.
-arturo
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-09-07 01:41:40 | Re: On DNS for postgresql.org |
Previous Message | Steve Atkins | 2006-09-07 01:23:06 | Re: On DNS for postgresql.org |