Re: BUG #16441: Cannot multi-insert into generated column withDEFAULT value - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #16441: Cannot multi-insert into generated column withDEFAULT value
Date
Msg-id 3a66b26f-0154-3216-1ed5-a63bf63ec61a@2ndquadrant.com
Whole thread Raw
In response to BUG #16441: Cannot multi-insert into generated column with DEFAULT value  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re : Re: BUG #16441: Cannot multi-insert into generated column with DEFAULT value  (Colin Darie <colin@darie.eu>)
List pgsql-bugs
On 2020-05-15 23:07, PG Bug reporting form wrote:
> Multiple inserts of DEFAULT value for generated columns are failing. Single
> inserts are OK.
> 
> 
> CREATE TABLE squares (num INTEGER NOT NULL, square INTEGER GENERATED ALWAYS
> AS (num * num) STORED);
> 
> 
> INSERT INTO squares(num, square) VALUES (1, DEFAULT);
> => INSERT 0 1
> INSERT INTO squares(num, square) VALUES (2, DEFAULT), (3, DEFAULT);
> => ERROR:  cannot insert into column "square"
> => DETAIL:  Column "square" is a generated column.

Yes, this has been reported before.  This is basically just not 
implemented.  Is there a reason you need to use this form, or are you 
just trying things out?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #16448: Remote code execution vulnerability
Next
From: Arthur Cheysson
Date:
Subject: Re: BUG #16283: crash on create index segmentation fault