| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SELECT INTO deprecation |
| Date: | 2020-12-02 20:35:46 |
| Message-ID: | 1672926.1606941346@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * 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.
> I don't see much value in this.
Yeah, if we want to kill it let's just do so. The negative language in
the reference page has been there since (at least) 7.1, so people can
hardly say they didn't see it coming.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-12-02 20:59:51 | Re: Commitfest 2020-11 is closed |
| Previous Message | Bruce Momjian | 2020-12-02 20:26:22 | Re: Add docs stub for recovery.conf |