Re: Bug: Cannot insert multiple records using DEFAULT keyword for generated column

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ryan Vinzent <ryan(dot)vinzent(at)invitae(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Bug: Cannot insert multiple records using DEFAULT keyword for generated column
Date: 2021-02-24 22:05:29
Message-ID: 4156696.1614204329@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ryan Vinzent <ryan(dot)vinzent(at)invitae(dot)com> writes:
> I have run into an issue and I'm fairly sure this can be classified as a bug.

More an unimplemented feature ...

> INSERT INTO
> "generated_column_table" ("name", "id_plus_one")
> VALUES
> ('some text', DEFAULT),
> ('other text', DEFAULT);
>
> ERROR: cannot insert into column "id_plus_one"
> DETAIL: Column "id_plus_one" is a generated column.

This works in HEAD, as of

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=17958972f

but there hasn't been any discussion of back-patching that.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-02-25 00:36:26 Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs
Previous Message PG Bug reporting form 2021-02-24 21:38:53 BUG #16896: pg_standby: Missing reference when building on Windows