From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: why generated columsn cannot be used in COPY TO?
Date: Fri, 6 Oct 2023 10:45:58 -0500
Message-ID: <7f80a4a3-af51-6863-b72d-bee1118b8f79@gmail.com> (raw)
In-Reply-To: <8cebb434-d1ff-2744-1ad0-63816019df04@a-kretschmer.de>
References: <CAKoxK+5=P6wJw=_UrzAQOBnGiHuq3kaXuPxuFh9_hTQc4nv89Q@mail.gmail.com>
<2949797.1696600071@sss.pgh.pa.us>
<8cebb434-d1ff-2744-1ad0-63816019df04@a-kretschmer.de>
On 10/6/23 09:04, Andreas Kretschmer wrote:
>
>
> 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
Nah. "The programmer -- and DBA -- on the Clapham omnibus" quite reasonably
expects that COPY table_name TO (output)" copies all the columns listed in
"\d table_name".
https://en.wikipedia.org/wiki/Man_on_the_Clapham_omnibus
"The man on the Clapham omnibus is a hypothetical ordinary and reasonable
person, used by the courts in English law where it is necessary to decide
whether a party has acted as a *reasonable person* would – for example, in a
civil action for negligence. The character is a *reasonably educated,
intelligent but nondescript person*, against whom the defendant's conduct
can be measured."
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: why generated columsn cannot be used in COPY TO?
In-Reply-To: <7f80a4a3-af51-6863-b72d-bee1118b8f79@gmail.com>
References: <CAKoxK+5=P6wJw=_UrzAQOBnGiHuq3kaXuPxuFh9_hTQc4nv89Q@mail.gmail.com> <2949797.1696600071@sss.pgh.pa.us> <8cebb434-d1ff-2744-1ad0-63816019df04@a-kretschmer.de> <7f80a4a3-af51-6863-b72d-bee1118b8f79@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox