Re: [PATCH] Implement INSERT SET syntax

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

To: Tom Lane <tgl@sss.pgh.pa.us>, David Steele <david@pgmasters.net>

Cc: Gareth Palmer <gareth@internetnz.net.nz>, Michael Paquier <michael@paquier.xyz>, Amit Kapila <amit.kapila16@gmail.com>, Vik Fearing <vik.fearing@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2020-03-25T12:51:25Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add const qualifiers to internal range type APIs
- 73025140885c 13.0 cited

On 2020-03-24 18:57, Tom Lane wrote:
> No doubt that's all fixable, but the realization that some cases of
> this syntax are*not*  just syntactic sugar for standards-compliant
> syntax is giving me pause.  Do we really want to get out front of
> the SQL committee on extending INSERT in an incompatible way?

What is the additional functionality that we are considering adding here?

The thread started out proposing a more convenient syntax, but it seems 
to go deeper now and perhaps not everyone is following.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services