| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SELECT INTO deprecation |
| Date: | 2021-01-30 10:29:44 |
| Message-ID: | bd018f4a-4ae9-386e-2cea-3464df62f980@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-12-17 02:30, Michael Paquier wrote:
> On Wed, Dec 16, 2020 at 06:07:08PM +0100, Peter Eisentraut wrote:
>> Right, we would very likely not add it now. But it doesn't seem to cause a
>> lot of ongoing maintenance burden, so if there is a use case, it's not
>> unreasonable to keep it around. I have no other motive here, I was just
>> curious.
>
> From the point of view of the code, this would simplify the grammar
> rules of SELECT, which is a good thing. And this would also simplify
> some code in the rewriter where we create some CreateTableAsStmt
> on-the-fly where an IntoClause is specified, but my take is that this
> is not really a burden when it comes to long-term maintenance. And
> the git history tells, at least it seems to me so, that this is not
> manipulated much.
I have committed my small documentation patch that points out
compatibility with other implementations.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2021-01-30 12:17:57 | Re: pgbench: option delaying queries till connections establishment? |
| Previous Message | Peter Eisentraut | 2021-01-30 08:51:03 | Re: Allow CURRENT_ROLE in GRANTED BY |