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

From Tom Lane
Subject Re: why generated columsn cannot be used in COPY TO?
Date
Msg-id 2949797.1696600071@sss.pgh.pa.us
Whole thread Raw
In response to why generated columsn cannot be used in COPY TO?  (Luca Ferrari <fluca1978@gmail.com>)
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?  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-general
Luca Ferrari <fluca1978@gmail.com> writes:
> 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?

There's a comment about that in copy.c:

 * We don't include generated columns in the generated full list and we don't
 * allow them to be specified explicitly.  They don't make sense for COPY
 * FROM, but we could possibly allow them for COPY TO.  But this way it's at
 * least ensured that whatever we copy out can be copied back in.

Not sure how convincing that reasoning is, but it was at least
thought about.  I do agree with it as far as the default column
list goes, but maybe we could allow explicit selection of these
columns in COPY TO.

            regards, tom lane



pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: why generated columsn cannot be used in COPY TO?
Next
From: Andreas Kretschmer
Date:
Subject: Re: why generated columsn cannot be used in COPY TO?