Re: Support for grabbing multiple consecutive values with nextval()

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Jille Timmermans <jille(at)quis(dot)cx>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Support for grabbing multiple consecutive values with nextval()
Date: 2022-02-28 10:13:23
Message-ID: cc1a80c9-1c6c-0502-f3fa-a6e03b180ade@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 27.02.22 10:42, Jille Timmermans wrote:
> I wanted to be able to allocate a bunch of numbers from a sequence at
> once. Multiple people seem to be struggling with this
> (https://stackoverflow.com/questions/896274/select-multiple-ids-from-a-postgresql-sequence,
> https://www.depesz.com/2008/03/20/getting-multiple-values-from-sequences/).
>
> I propose to add an extra argument to nextval() that specifies how many
> numbers you want to allocate (default 1).

What is the use of this?

I note that the stackoverflow question wanted to return multiple
sequence values as a result set, whereas your implementation just skips
a number of values and returns the last one. At least we should be
clear about what we are trying to achieve.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-02-28 10:22:02 Re: Proposal: Support custom authentication methods using hooks
Previous Message Peter Eisentraut 2022-02-28 09:56:27 Re: unlogged sequences