Skip site navigation (1) Skip section navigation (2)

Re: session_id

From: "Riccardo G(dot) Facchini" <abief_ag_-postgresql(at)yahoo(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-sql(at)postgresql(dot)org
Subject: Re: session_id
Date: 2004-11-18 12:38:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
--- Michael Fuhr <__> wrote:

> 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.
> Can you give us an example of where this wouldn't work?

No, I can't provide it because your'e right. currval() is NOT affected
by other sessions.

Thanks anyway for the suggestion, using pg_backend_pid() solved the
uniqueness I needed. I'll keep the nextval/currval for another

thanks to all for the support!

In response to


pgsql-sql by date

Next:From: Justine.ClearyDate: 2004-11-18 19:28:03
Subject: missing... at end of sql expression
Previous:From: Premsun CholtanwanichDate: 2004-11-18 10:45:12
Subject: How to make lo_import and lo_export to use file on clientlocal machine?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group