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

From Michael Glaesemann
Subject Re: collision in serial numbers after INSERT?
Date
Msg-id ACDD9CBF-E03C-4D12-B194-3A7F9C28147E@seespotcode.net
Whole thread Raw
In response to Re: collision in serial numbers after INSERT?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Jun 1, 2007, at 15:00 , Tom Lane wrote:

> Michael Glaesemann <grzm@seespotcode.net> writes:
>> On May 31, 2007, at 11:46 , lawpoop@gmail.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.

I read that much too quickly. My apologies, lawpoop. And thanks, Tom.

Michael Glaesemann
grzm seespotcode net



pgsql-general by date:

Previous
From: Ron St-Pierre
Date:
Subject: [Fwd: Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum]
Next
From: Alvaro Herrera
Date:
Subject: Re: [Fwd: Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum]