Re: [PATCH] Implement INSERT SET syntax

Gareth Palmer <gareth@internetnz.net.nz>

From: Gareth Palmer <gareth@internetnz.net.nz>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Amit Kapila <amit.kapila16@gmail.com>, Vik Fearing <vik.fearing@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2019-11-21T23:24:15Z

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

Attachments

insert-set-v4.patch (application/octet-stream) patch v4

> On 19/11/2019, at 5:05 PM, Gareth Palmer <gareth@internetnz.net.nz> wrote:
>> 
>> Since nobody has objected to this, I'm supposing that there's general
>> consensus that that design sketch is OK, and we can move on to critiquing
>> implementation details.  I took a look, and didn't like much of what I saw.

Attached is an updated patch with for_locking_clause added, test-cases
re-use existing tables and the comments and documentation have been
expanded.

>> I'm setting this back to Waiting on Author.