Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kknXS-0002Bw-Qu for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Dec 2020 12:16:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kknXR-0001Hj-Qv for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Dec 2020 12:16:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kknXR-0001Hb-Jo for pgsql-hackers@lists.postgresql.org; Thu, 03 Dec 2020 12:16:45 +0000 Received: from forward4-smtp.messagingengine.com ([66.111.4.238]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kknXJ-0005wd-FR for pgsql-hackers@postgresql.org; Thu, 03 Dec 2020 12:16:44 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailforward.nyi.internal (Postfix) with ESMTP id 7C3F519433C3; Thu, 3 Dec 2020 07:16:35 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 03 Dec 2020 07:16:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=r34o9jo5TMHWKNQ6729+ElbJ4BdwaSXptwimIBxju +w=; b=RflKVN4yRwpsq23KAdMp+HWvqR5e1eNqPEiqSIOOAUeyQkbsK9k48cUV8 MyV4msPZ4WS8l4xmSArQq97H3R3vbEqUdf1N9bq4I1gzuWfMETgixiSkkDe4lm2S 7f8A4F4AziVhIggFgBEm0SRdnkCHRMeZuxV4w7sOUZMJYSqg3JlYH4YfOPNNteKM SlY1wB6aEPeSj0W02iVrgtbuevjIw/AoROPeGSbyRBjXqCr8uBUgmy0H0tuigvXz qQkUwVnY2RCIRVl/6T8iYFKzvJAE56jcY42PRIGeRd03Tw8bBVg4kmGCAgihOYD5 rTy/P9LfrbCFR3987axZmFx2MbP5w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeiiedgfeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeehnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeffvdeufedtgffgveff vdehjeekjeekhedvvdeuheeghfffledvgffffffffeejudenucfkphepkeejrddujeejrd ejvddrudegvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtoh hm X-ME-Proxy: Received: from april.pezone.net (p57b1488e.dip0.t-ipconnect.de [87.177.72.142]) by mail.messagingengine.com (Postfix) with ESMTPA id 9F8E41080057; Thu, 3 Dec 2020 07:16:33 -0500 (EST) Subject: Re: SELECT INTO deprecation To: Michael Paquier , Tom Lane References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com> <20201202175836.GX16415@tamriel.snowman.net> <1672926.1606941346@sss.pgh.pa.us> Cc: Stephen Frost , pgsql-hackers From: Peter Eisentraut Organization: EnterpriseDB Message-ID: <8e05fc79-abca-dd3f-4d48-8aaae9525a8f@enterprisedb.com> Date: Thu, 3 Dec 2020 13:16:32 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-12-03 00:54, Michael Paquier wrote: > I got to wonder about the impact when migrating applications > though. SELECT INTO has a different meaning in Oracle, but SQL server > creates a new table like Postgres. Interesting. This appears to be the case. SQL Server uses SELECT INTO to create a table, and does not appear to have CREATE TABLE AS. So maybe we should keep it, but adjust the documentation to point out this use case. [some snarky comment about AWS Babelfish here ... ;-) ]