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

Re: BUG #3811: Getting multiple values from asequence generator

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Adriaan van Os <postgres(at)microbizz(dot)nl>
Cc: pgsql-bugs(at)postgresql(dot)org, depesz(at)depesz(dot)com
Subject: Re: BUG #3811: Getting multiple values from asequence generator
Date: 2007-12-14 10:20:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
On Fri, 2007-12-14 at 10:47 +0100, Adriaan van Os wrote:
> Simon Riggs wrote:
> > On Mon, 2007-12-10 at 12:31 +0100, hubert depesz lubaczewski wrote:
> >> On Sun, Dec 09, 2007 at 03:32:17PM +0000, Simon Riggs wrote:
> >> this has the sideeffect that all concurrent nextvals() will also
> >> increment by val, which is not always acceptable.
> > 
> > So this is a feature proposal, not a bug? 
> > 
> > Sounds interesting but needs to be on pgsql-hackers, please.
> I posted a message to pgsql-hackers three times but it gets stalled (and the owner of the list 
> doesn't reply).

Somebody will need to join pgsql-hackers. Other mail will be reflected
because of spam.

  Simon Riggs

In response to


pgsql-hackers by date

Next:From: Michael AkindeDate: 2007-12-14 10:59:51
Subject: Re: VACUUM ANALYZE out of memory
Previous:From: Zeugswetter Andreas ADI SDDate: 2007-12-14 09:51:35
Subject: Re: [GENERAL] Slow PITR restore

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2007-12-14 11:20:51
Subject: Re: BUG #3811: Getting multiple values from a sequencegenerator
Previous:From: Bruce MomjianDate: 2007-12-13 00:34:05
Subject: Re: BUG #3774: create table like including index doesn't update pg_constraints with primary key

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