why generated columsn cannot be used in COPY TO? - Mailing list pgsql-general

From Luca Ferrari
Subject why generated columsn cannot be used in COPY TO?
Date
Msg-id CAKoxK+5=P6wJw=_UrzAQOBnGiHuq3kaXuPxuFh9_hTQc4nv89Q@mail.gmail.com
Whole thread Raw
Responses Re: why generated columsn cannot be used in COPY TO?  (Andreas Kretschmer <andreas@a-kretschmer.de>)
Re: why generated columsn cannot be used in COPY TO?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi all,
I'm wondering why in COPY TO (file or program) I cannot use generated
columns: since I'm pushing data out of the table, why they are not
allowed?

Example:

testdb=# CREATE TABLE test( pk int generated always as identity primary key
, ts timestamp default current_timestamp
, month int generated always as ( extract( month from ts ) ) stored
);

testdb=# insert into test( ts ) values( current_timestamp );

testdb=# copy test to program 'head'; -- ok but silently removes the column
COPY 1
testdb=# copy test( month ) to program 'head';
ERROR:  column "month" is a generated column
DETAIL:  Generated columns cannot be used in COPY.

Thanks,
Luca



pgsql-general by date:

Previous
From: Anuwat Sagulmontreechai
Date:
Subject: RE: Ask about Foreign Table Plug-in on Windows Server.
Next
From: Andreas Kretschmer
Date:
Subject: Re: why generated columsn cannot be used in COPY TO?