From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ryan Vinzent <ryan.vinzent@invitae.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Bug: Cannot insert multiple records using DEFAULT keyword for generated column
Date: Wed, 24 Feb 2021 17:05:29 -0500
Message-ID: <4156696.1614204329@sss.pgh.pa.us> (raw)
In-Reply-To: <CAJJLo9Wt2Xd06xeuiUH5YWg145Eu2iFAj1Q4YYsa-TO16RBsKQ@mail.gmail.com>
References: <CAJJLo9Wt2Xd06xeuiUH5YWg145Eu2iFAj1Q4YYsa-TO16RBsKQ@mail.gmail.com>
Ryan Vinzent <ryan.vinzent@invitae.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, ryan.vinzent@invitae.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Bug: Cannot insert multiple records using DEFAULT keyword for generated column
In-Reply-To: <4156696.1614204329@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox