Postgres Pro
Downloads
Home   >   mailing lists

Re: Support for grabbing multiple consecutive values with nextval() - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Support for grabbing multiple consecutive values with nextval()
Date
Msg-id Y0ZSxNu/+bzzaIzu@paquier.xyz
Whole thread Raw
In response to Support for grabbing multiple consecutive values with nextval()  (Jille Timmermans <jille@quis.cx>)
List pgsql-hackers
Tree view 
On Sat, Jul 30, 2022 at 04:21:07PM +0900, Michael Paquier wrote:
> FWIW, I find the result set approach more intuitive and robust,
> particularly in the case of a sequence has non-default values
> INCREMENT and min/max values.  This reduces the dependency of what an
> application needs to know about the details of a given sequence.  With
> only the last value reported, the application would need to compile
> things by itself.

It seems like there is a consensus here, but the thread has no
activity for the past two months, so I have marked the patch as
returned with feedback for now.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_checksum: add test for coverage
Next
From: Michael Paquier
Date:
Subject: Re: remove_useless_groupby_columns is too enthusiastic