From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: SELECT INTO deprecation
Date: Thu, 3 Dec 2020 13:16:32 +0100
Message-ID: <8e05fc79-abca-dd3f-4d48-8aaae9525a8f@enterprisedb.com> (raw)
In-Reply-To: <X8gpP9GL7R5AsF3E@paquier.xyz>
References: <96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com>
<20201202175836.GX16415@tamriel.snowman.net>
<1672926.1606941346@sss.pgh.pa.us>
<X8gpP9GL7R5AsF3E@paquier.xyz>
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 ... ;-) ]
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, michael@paquier.xyz, tgl@sss.pgh.pa.us, sfrost@snowman.net
Subject: Re: SELECT INTO deprecation
In-Reply-To: <8e05fc79-abca-dd3f-4d48-8aaae9525a8f@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