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

From: Jille Timmermans <jille(at)quis(dot)cx>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Support for grabbing multiple consecutive values with nextval()
Date: 2022-03-02 19:12:20
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2022-02-28 11:13, Peter Eisentraut wrote:
> 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
>> (,
>> 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.
Both would work for me actually. I'm using COPY FROM to insert many rows
and need to know their ids and COPY FROM doesn't support RETURNING.

I implemented this approach because:
- smaller diff
- maybe someone benefits from them being consecutive
- less data to send between client/server

The obvious downside is that people can make mistakes in whether the
returned number is the first or last number of the series.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2022-03-02 19:23:51 Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Previous Message Laurenz Albe 2022-03-02 19:07:12 Re: [PATCH] Add reloption for views to enable RLS