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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Jille Timmermans <jille(at)quis(dot)cx>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Support for grabbing multiple consecutive values with nextval()
Date: 2022-07-08 10:27:27
Message-ID: YsgGj4xaoYczpwf2@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 03, 2022 at 10:21:05AM +0100, Jille Timmermans wrote:
> I'm using https://pkg.go.dev/github.com/jackc/pgx/v4#Conn.CopyFrom, which
> uses the COPY FROM protocol but doesn't actually have to originate from a
> file.

It is Friday here, so I would easily miss something.. It is possible
to use COPY FROM with a list of columns, so assuming that you could
use a default expression with nextval() or just a SERIAL column not
listed in the COPY FROM query to do the job, what do we gain with this
feature? In which aspect does the preallocation of a range handled
on the client side after being allocated in the backend make things
better?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-07-08 11:08:57 Re: Handle infinite recursion in logical replication setup
Previous Message Yugo NAGATA 2022-07-08 10:22:11 Re: Implementing Incremental View Maintenance