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 1kkYqv-0004BU-UN for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Dec 2020 20:35:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kkYqu-0001Lv-GP for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Dec 2020 20:35:52 +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 1kkYqu-0001Lo-95 for pgsql-hackers@lists.postgresql.org; Wed, 02 Dec 2020 20:35:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kkYqs-0006Kp-3f for pgsql-hackers@postgresql.org; Wed, 02 Dec 2020 20:35:51 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0B2KZk7a1672927; Wed, 2 Dec 2020 15:35:46 -0500 From: Tom Lane To: Stephen Frost cc: Peter Eisentraut , pgsql-hackers Subject: Re: SELECT INTO deprecation In-reply-to: <20201202175836.GX16415@tamriel.snowman.net> References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com> <20201202175836.GX16415@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Wed, 02 Dec 2020 12:58:36 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1672925.1606941346.1@sss.pgh.pa.us> Date: Wed, 02 Dec 2020 15:35:46 -0500 Message-ID: <1672926.1606941346@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stephen Frost writes: > * Peter Eisentraut (peter.eisentraut@enterprisedb.com) wrote: >> While reading about deprecating and removing various things in other >> threads, I was wondering about how deprecated SELECT INTO is. There are >> various source code comments about this, but the SELECT INTO reference page >> only contains soft language like "recommended". I'm proposing the attached >> patch to stick a more explicit deprecation notice right at the top. > I don't see much value in this. Yeah, if we want to kill it let's just do so. The negative language in the reference page has been there since (at least) 7.1, so people can hardly say they didn't see it coming. regards, tom lane