| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| 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: | 2020-12-17 01:30:17 |
| Message-ID: | X9q0qXzF7c+clssU@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2020-12-17 01:32:25 | Re: [HACKERS] logical decoding of two-phase transactions |
| Previous Message | Justin Pryzby | 2020-12-17 01:28:31 | [PATCH] nbtree: Do not show debugmessage if deduplication is disabled |