From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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: Thu, 3 Dec 2020 08:54:39 +0900
Message-ID: <X8gpP9GL7R5AsF3E@paquier.xyz> (raw)
In-Reply-To: <1672926.1606941346@sss.pgh.pa.us>
References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com>
<20201202175836.GX16415@tamriel.snowman.net>
<1672926.1606941346@sss.pgh.pa.us>
On Wed, Dec 02, 2020 at 03:35:46PM -0500, Tom Lane wrote:
> 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.
+1. 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.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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: michael@paquier.xyz, tgl@sss.pgh.pa.us, sfrost@snowman.net, peter.eisentraut@enterprisedb.com
Subject: Re: SELECT INTO deprecation
In-Reply-To: <X8gpP9GL7R5AsF3E@paquier.xyz>
* 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