| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SELECT INTO deprecation |
| Date: | 2020-12-03 12:14:11 |
| Message-ID: | 01923635-387c-c3fd-d9f9-7f91f20e426b@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-12-02 18:58, Stephen Frost wrote:
>> 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.
> If we aren't actually removing SELECT INTO then I don't know that it
> makes sense to just stop testing it.
The point here was, there is still code that actually tests SELECT INTO
specifically. But unrelated test code that just wants to set up a quick
table with some rows in it ought to use the preferred syntax for doing so.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-12-03 12:16:32 | Re: SELECT INTO deprecation |
| Previous Message | Fujii Masao | 2020-12-03 12:09:32 | Re: autovac issue with large number of tables |