Re: SELECT INTO deprecation - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: SELECT INTO deprecation
Date
Msg-id CAFj8pRBSirDotmvook8pkqV16Y6P3+2JtAhHD2okj9tvBEBePA@mail.gmail.com
Whole thread Raw
In response to SELECT INTO deprecation  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers


st 2. 12. 2020 v 12:55 odesílatel Peter Eisentraut <peter.eisentraut@enterprisedb.com> napsal:
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 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.

I don't have a specific plan for removing top-level SELECT INTO
altogether, but there is a nontrivial amount of code for handling it, so
there would be some gain if it could be removed eventually.

+1

Pavel

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Deprecate custom encoding conversions
Next
From: Tom Lane
Date:
Subject: Re: Deprecate custom encoding conversions