Horton

Re: [PATCH] Implement INSERT SET syntax

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

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: wenjing zeng <wjzeng2012@gmail.com>, Rachel Heaton <rachelmheaton@gmail.com>, Gareth Palmer <gareth@internetnz.net.nz>, movead li <movead.li@highgo.ca>, david@pgmasters.net, Ibrar Ahmed <ibrar.ahmad@gmail.com>, pgsql-hackers@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Date: 2022-03-23T15:32:51Z
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 →

  1. Add const qualifiers to internal range type APIs

Justin Pryzby <pryzby@telsasoft.com> writes:
> You have to either include the pre-requisite patches as 0001, and your patch as
> 0002 (as I'm doing now), or name your patch something other than *.diff or
> *.patch, so cfbot doesn't think it's a new version of the patch to be tested.

This patch has been basically ignored for a full two years now.
(Remarkably, it's still passing in the cfbot.)

I have to think that that means there's just not enough interest
to justify committing it.  Should we mark it rejected and move on?
If not, what needs to happen to get it unstuck?

			regards, tom lane