pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: 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 08:53:28 -0700
Message-ID: <4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.com> (raw)
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>

On 10/6/23 08:45, Ron wrote:
> On 10/6/23 09:04, Andreas Kretschmer wrote:
>>

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

Yeah, I would agree.

> -- 
> Born in Arizona, moved to Babylonia.

-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (14+ messages)  latest in thread

Message-ID: <4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.com>
Permalink:  ../4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.com/
Also on:    postgresql.org/message-id/4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.com

 · 

reply

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: adrian.klaver@aklaver.com, ronljohnsonjr@gmail.com
  Subject: Re: why generated columsn cannot be used in COPY TO?
  In-Reply-To: <4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.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> <4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.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