Re: SELECT INTO deprecation

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SELECT INTO deprecation
Date: 2020-12-16 17:07:08
Message-ID: b2f854c2-f780-c739-064c-cb856e9e213f@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-12-15 23:13, Bruce Momjian wrote:
> Do we really want to carry around confusing syntax for compatibility? I
> doubt we would ever add INTO now, even for compatibility.

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-12-16 17:15:00 Re: Deadlock between backend and recovery may not be detected
Previous Message Stephen Frost 2020-12-16 16:26:46 Re: Proposed patch for key managment