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

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Jille Timmermans <jille(at)quis(dot)cx>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Support for grabbing multiple consecutive values with nextval()
Date: 2022-02-27 13:22:50
Message-ID: 20220227132250.hdtkvb46qgy5rvly@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Sun, Feb 27, 2022 at 10:42:25AM +0100, Jille Timmermans wrote:
>
> First time PostgreSQL contributor here :)

Welcome!

> 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).
>
> The attached patch (based on master) passes `./configure --enable-cassert
> --enable-debug && make && make check`, including the newly added regression
> tests.
>
> It does change the signature of nextval_internal(), not sure if that's
> considered backwards compatibility breaking (for extensions?).

Please register this patch to the next commit fest (and last for pg15
inclusion) at https://commitfest.postgresql.org/37/ if not done already.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gunnar "Nick" Bluth 2022-02-27 13:30:33 Re: PATCH: add "--config-file=" option to pg_rewind
Previous Message Michael Paquier 2022-02-27 12:08:56 Re: pg_stat_statements: remove redundant function call in pg_stat_statements_internal