Re: collision in serial numbers after INSERT?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Glaesemann <grzm(at)seespotcode(dot)net>
Cc: lawpoop(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: collision in serial numbers after INSERT?
Date: 2007-06-01 20:00:34
Message-ID: 22658.1180728034@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
> On May 31, 2007, at 11:46 , lawpoop(at)gmail(dot)com wrote:
>> However, I wondered, if I were in an environment where there were many
>> concurrent inserts, would it be possible that I didn't get the serial
>> number of the insert that *I* just did?

> No.

Uh, yes, because he was using "SELECT last_value FROM seq" which is
indeed subject to race conditions. currval() would be far safer.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2007-06-01 20:02:14 Re: multimaster
Previous Message Tom Lane 2007-06-01 19:50:55 Re: Slightly OT.