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

From Andreas Kretschmer
Subject Re: why generated columsn cannot be used in COPY TO?
Date
Msg-id 8cebb434-d1ff-2744-1ad0-63816019df04@a-kretschmer.de
Whole thread Raw
In response to Re: why generated columsn cannot be used in COPY TO?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: why generated columsn cannot be used in COPY TO?
List pgsql-general

Am 06.10.23 um 15:47 schrieb Tom Lane:
> 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.

ha, as always: read the source ;-)

>
> 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.

sounds okay


Andreas

-- 
Andreas Kretschmer - currently still (garden leave)
Technical Account Manager (TAM)
www.enterprisedb.com




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: why generated columsn cannot be used in COPY TO?
Next
From: Artur Zakirov
Date:
Subject: Re: How to make a map in pg kernel?