pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ross J. Reedstrom <reedstrm@rice.edu>
To: pgsql-sql@postgresql.org
Subject: Re: INSERT question
Date: Fri, 16 Nov 2001 11:03:07 -0600
Message-ID: <20011116110306.A7689@rice.edu> (raw)
In-Reply-To: <87lmh6u02k.fsf@npa01zz001.simplot.com>
References: <1f5f2b44.0111130130.17e8e57a@posting.google.com>
	<3bf19679$0$189$e4fe514c@newszilla.xs4all.nl>
	<878zd7vpzn.fsf@npa01zz001.simplot.com>
	<m21yizhkej.fsf@tycho.rlent.pnet>
	<87y9l7u3k5.fsf@npa01zz001.simplot.com>
	<20011115160902.E4187@rice.edu>
	<87lmh6u02k.fsf@npa01zz001.simplot.com>

No apologies necessary: if anything, _I_ was the one getting a little
too gruff. In fact, _this_ time we did uncover a new aspect of this
problem: connection pooling can get in the way.

Ross

On Fri, Nov 16, 2001 at 09:56:03AM -0700, Jason Earl wrote:
> 
> Thanks for being patient with me.  I must have fallen on my head
> yesterday or something.  I *knew* currval and nextval were backend
> specific.  I got confused because I am working on a middleware layer
> with a connection pool that grabs a connection and holds it until the
> transaction is finished.  Each new transaction might grab a different
> backend, but you won't get a new backend until your transaction is
> finished.
> 
> In other words, in my application the easiest way to insure that
> currval and nextval work like they should is to start a transaction
> (which grabs a backend connection).
> 
> Apparently this has led to some very fuzzy thinking on my part.  My
> apologies for sending contradictory and confusing posts to the list,
> and thanks for clearing that up.
> 
> Jason



view thread (12+ messages)

Message-ID: <20011116110306.A7689@rice.edu>
Permalink:  ../20011116110306.A7689@rice.edu/
Also on:    postgresql.org/message-id/20011116110306.A7689@rice.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: reedstrm@rice.edu
  Subject: Re: INSERT question
  In-Reply-To: <20011116110306.A7689@rice.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox