Re: collision in serial numbers after INSERT? - Mailing list pgsql-general

From Steve Lefevre
Subject Re: collision in serial numbers after INSERT?
Date
Msg-id 4660A57C.6050101@osu.edu
Whole thread Raw
In response to Re: collision in serial numbers after INSERT?  (Bill Moran <wmoran@potentialtech.com>)
Responses Re: collision in serial numbers after INSERT?
List pgsql-general
Bill Moran wrote:
> Don't do that. Please let us know what site recommended that so I can
> send an email to the author correcting them.
>
Hello Bill -

The 'offending' site and article is at
http://www.sitepoint.com/article/site-mysql-postgresql-2/3

> Instead, do SELECT currval('<seqname>'), which is guaranteed to be isolated
> from other sessions.
>
I've also gotten other advice to SELECT next_val ( whatever the exact
wording is) will reserve that serial number for you. Is that true?

So l
> If you use the code above, sooner or later you're going to get bit.
>
Thanks!


pgsql-general by date:

Previous
From: Lew
Date:
Subject: Re: Delete with subquery deleting all records
Next
From: Lew
Date:
Subject: Re: There can be only one! How to avoid the "highlander-problem".