Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qon91-002uEF-G8 for pgsql-general@arkaria.postgresql.org; Fri, 06 Oct 2023 15:53:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qon8x-008lJb-80 for pgsql-general@arkaria.postgresql.org; Fri, 06 Oct 2023 15:53:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qon8w-008lIj-9C for pgsql-general@lists.postgresql.org; Fri, 06 Oct 2023 15:53:35 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qon8t-000cXh-DM for pgsql-general@lists.postgresql.org; Fri, 06 Oct 2023 15:53:34 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0DCF35C027D; Fri, 6 Oct 2023 11:53:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 06 Oct 2023 11:53:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1696607610; x=1696694010; bh=GAwjlhVP/k8zCQXsCPFlAiI7ihT8RyMYIZE HdlhaRuA=; b=TNF7U3g8bIoVkb9bN7ZBhC83LoP3wvOx0dFtMoCai7g+RI5BYxq 8Hqs35FOOr3lyMd5SWrM2Y2vY5i+L9k7gybSBIOYqCmvEl6vqZI4+Q0Joe/r+eQB HPjTNW9r/zlVluwkhp/iR+Z3fw6p1+QO3aJW/ASa9NtGgM5Mrkz8JPqpfwn+A/MR HBlgykoPGS/fy4dmSOzO+mjLzFx5PRoOSPeAzzlnRjpvhpZkazpvzntAmvKtZxBw HEhhYhUDmsc6JOES6q7yn2CoT86AoAdq2pLmz2yuXs9lLbtFYVEPiyVxGuO/Y3wn 7PYJcEFVhMkppVvPX83zezUIFzra2wLPZcA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1696607610; x= 1696694010; bh=GAwjlhVP/k8zCQXsCPFlAiI7ihT8RyMYIZEHdlhaRuA=; b=C rchT7S6cp/knypH9PXjk0Trgp8LifXAYC7FqL018tei8SWneMcc4uhinO6L6GUse KLlzD5dDcKYkdz7bJJHwUdHAIQcgbkr9sdfc+ztqq+5s6+yFVDzR4TF/q4Fy+uoG cNC8MsM0gaD04UDq64P1++0U807kH6zjM+XOVcnNz+kVRfv/8xa8WbNw3ydRK/RY bSIePhPKRV0iFWP7gOCzsRgoVGlhj/5Es5l3Yh4mpkL1OGXVwIQPHgIRqK1J6Wdx kZJ1/+t+gRx/lk4Nsq6xk+YpL1U8QWGLCA4707Tyv1NFB9D2KlJwfsOxdljoC+96 6Jgd7FvM4Qx/nMUahMM2A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrgeeigdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeffleegieefgf evudehtdfhkeeutdffjeevgeffgeejvedthefgudeiteefheejheenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 6 Oct 2023 11:53:29 -0400 (EDT) Message-ID: <4edb5259-10e6-4103-9d4b-9d63992a6a91@aklaver.com> Date: Fri, 6 Oct 2023 08:53:28 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: why generated columsn cannot be used in COPY TO? To: Ron , pgsql-general@lists.postgresql.org References: <2949797.1696600071@sss.pgh.pa.us> <8cebb434-d1ff-2744-1ad0-63816019df04@a-kretschmer.de> <7f80a4a3-af51-6863-b72d-bee1118b8f79@gmail.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <7f80a4a3-af51-6863-b72d-bee1118b8f79@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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