Re: SELECT INTO deprecation - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: SELECT INTO deprecation
Date
Msg-id X9q0qXzF7c+clssU@paquier.xyz
Whole thread Raw
In response to Re: SELECT INTO deprecation  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: SELECT INTO deprecation
List pgsql-hackers
On Wed, Dec 16, 2020 at 06:07:08PM +0100, Peter Eisentraut wrote:
> Right, we would very likely not add it now.  But it doesn't seem to cause a
> lot of ongoing maintenance burden, so if there is a use case, it's not
> unreasonable to keep it around.  I have no other motive here, I was just
> curious.

From the point of view of the code, this would simplify the grammar
rules of SELECT, which is a good thing.  And this would also simplify
some code in the rewriter where we create some CreateTableAsStmt
on-the-fly where an IntoClause is specified, but my take is that this
is not really a burden when it comes to long-term maintenance.  And
the git history tells, at least it seems to me so, that this is not
manipulated much.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: [PATCH] nbtree: Do not show debugmessage if deduplication is disabled
Next
From: Ajin Cherian
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions