From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: SELECT INTO deprecation
Date: Thu, 3 Dec 2020 13:14:11 +0100
Message-ID: <01923635-387c-c3fd-d9f9-7f91f20e426b@enterprisedb.com> (raw)
In-Reply-To: <20201202175836.GX16415@tamriel.snowman.net>
References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com>
<20201202175836.GX16415@tamriel.snowman.net>
On 2020-12-02 18:58, Stephen Frost wrote:
>> I also found some gratuitous uses of SELECT INTO in various tests and
>> documentation (not ecpg or plpgsql of course). Here is a patch to adjust
>> those to CREATE TABLE AS.
> If we aren't actually removing SELECT INTO then I don't know that it
> makes sense to just stop testing it.
The point here was, there is still code that actually tests SELECT INTO
specifically. But unrelated test code that just wants to set up a quick
table with some rows in it ought to use the preferred syntax for doing so.
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: peter.eisentraut@enterprisedb.com, sfrost@snowman.net
Subject: Re: SELECT INTO deprecation
In-Reply-To: <01923635-387c-c3fd-d9f9-7f91f20e426b@enterprisedb.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