| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: why generated columsn cannot be used in COPY TO? |
| Date: | 2023-10-06 13:47:51 |
| Message-ID: | 2949797.1696600071@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Luca Ferrari <fluca1978(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2023-10-06 14:04:33 | Re: why generated columsn cannot be used in COPY TO? |
| Previous Message | Ron | 2023-10-06 13:16:35 | Re: why generated columsn cannot be used in COPY TO? |