Re: [GENERAL] get the previous assigned sequence value - Mailing list pgsql-general

From Ed Loehr
Subject Re: [GENERAL] get the previous assigned sequence value
Date
Msg-id 384FED8C.CF02D1FE@austin.rr.com
Whole thread Raw
In response to get the previous assigned sequence value  (Kevin Heflin <kheflin@shreve.net>)
Responses Re: [GENERAL] get the previous assigned sequence value  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [GENERAL] get the previous assigned sequence value  (<kaiq@realtyideas.com>)
List pgsql-general
"Ross J. Reedstrom" wrote:

> Gah, this is getting a bit annoying, correcting this bit of
> mis-information.
>
> currval() is kept as part of the session context, as is completely
> multi-user safe. That's why the person you quoted said 'in the same
> session'.
>
> Where is everyone coming up with the wrong idea on this? Is there a
> major commercial DB with sequence objects that gets this wrong?

I think it is primarily because (a) it is intuitive to think there is a race
condition, which fortunately psgql folks have gone to significant efforts to
avoid, and (b) the documentation at

    http://www.postgresql.org/docs/postgres/sql-createsequence.htm

is less than concise/clear on this issue.

Same thing is true for the question of how to retrieve the newly-inserted
serial, which is why people keep asking the same question over and over (that,
and because people don't know about www.deja.com or the mailing list search
engine...or the engine is broken).

Cheers.
Ed





pgsql-general by date:

Previous
From: soundar rajan
Date:
Subject: JDBC2.0 and pg
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] get the previous assigned sequence value