From: Tom Lane <tgl@sss.pgh.pa.us>
To: n5jgvx4@nate.sh
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16969: INSERT of multiple rows into GENERATED ALWAYS AS
 IDENTITY column with DEFAULT value is broken.
In-reply-to: <16969-e14b6d95e35f939c@postgresql.org>
References: <16969-e14b6d95e35f939c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 17 Apr 2021 11:18:38 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <256833.1618672571.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 17 Apr 2021 11:16:11 -0400
Message-ID: <256834.1618672571@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/256834.1618672571%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> -- insert more than one row with "id" set to DEFAULT;
> -- result: unexpected and undocumented failure with the following error:
> --     ERROR:  cannot insert into column "id"
> --     DETAIL:  Column "id" is an identity column defined as GENERATED
> ALWAYS.
> --     HINT:  Use OVERRIDING SYSTEM VALUE to override.
> INSERT INTO test (id, name) VALUES (DEFAULT, 'Adam'), (DEFAULT, 'Eve');

Yeah, this is a known deficiency.  It's fixed for v14, but the
fix was deemed too invasive to risk back-patching [1].

			regards, tom lane

[1] https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h=
=3D17958972f