Re: BUG #16969: INSERT of multiple rows into GENERATED ALWAYS AS IDENTITY column with DEFAULT value is broken. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16969: INSERT of multiple rows into GENERATED ALWAYS AS IDENTITY column with DEFAULT value is broken.
Date
Msg-id 256834.1618672571@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16969: INSERT of multiple rows into GENERATED ALWAYS AS IDENTITY column with DEFAULT value is broken.  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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=postgresql.git&a=commitdiff&h=17958972f



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: function to_char
Next
From: Valentin Gatien-Baron
Date:
Subject: websearch_to_tsquery() returns queries that don't match to_tsvector()