Date: Wed, 17 Nov 2004 08:19:39 -0700
From: Michael Fuhr <mike@fuhr.org>
To: "Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com>
Cc: Richard Huxton <dev@archonet.com>, pgsql-sql@postgresql.org
Subject: Re: session_id
Message-ID: <20041117151939.GA4078@winnie.fuhr.org>
References: <419B56CC.8090703@archonet.com>
	<20041117142525.97895.qmail@web13924.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041117142525.97895.qmail@web13924.mail.yahoo.com>

On Wed, Nov 17, 2004 at 06:25:25AM -0800, Riccardo G. Facchini wrote:
> 
> --- Richard Huxton <__> wrote:
> >
> > Add a new sequence to your database:

[snip]

> Good idea, but it won't work for what I need.
> I'll be able to do get the nextval('my_session_id') as soon as the
> session initiates, but my problem is that I need to make all the
> subsecuent actions aware of that particular value. using
> currval('my_session_id') is not good, as any other session is likely to
> also change my_session_id to another value.

Where did you get the idea that currval() would be affected by other
sessions?  Richard mentioned that sequences are concurrency-safe,
as does the documentation.

http://www.postgresql.org/docs/7.4/static/functions-sequence.html

Can you give us an example of where this wouldn't work?

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/