From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: SELECT INTO deprecation
Date: Wed, 02 Dec 2020 15:35:46 -0500
Message-ID: <1672926.1606941346@sss.pgh.pa.us> (raw)
In-Reply-To: <20201202175836.GX16415@tamriel.snowman.net>
References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com>
<20201202175836.GX16415@tamriel.snowman.net>
Stephen Frost <sfrost@snowman.net> 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
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, sfrost@snowman.net, peter.eisentraut@enterprisedb.com
Subject: Re: SELECT INTO deprecation
In-Reply-To: <1672926.1606941346@sss.pgh.pa.us>
* 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