Re: SELECT INTO deprecation

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SELECT INTO deprecation
Date: 2020-12-02 12:08:47
Message-ID: A7CE8370-5F62-4714-8CC8-4F607D5ABF27@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Dec 2020, at 12:54, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:

> 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.

+ This command is deprecated. Use <link
Should this get similar strong wording to other deprecated things where we add
"..and may/will eventually be removed"?

> 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 didn't scan for others, but the ones included in the 0001 patch all looks
fine and IMO improves readability.

cheers ./daniel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2020-12-02 12:39:42 Re: proposal: unescape_text function
Previous Message Peter Eisentraut 2020-12-02 11:54:48 SELECT INTO deprecation