SELECT INTO deprecation - Mailing list pgsql-hackers

From Peter Eisentraut
Subject SELECT INTO deprecation
Date
Msg-id 96dc0df3-e13a-a85d-d045-d6e2c85218da@enterprisedb.com
Whole thread Raw
Responses Re: SELECT INTO deprecation
Re: SELECT INTO deprecation
Re: SELECT INTO deprecation
List pgsql-hackers
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.

Attachment

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: Daniel Gustafsson
Date:
Subject: Re: SELECT INTO deprecation