Re: [PATCH] Implement INSERT SET syntax

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, wenjing zeng <wjzeng2012(at)gmail(dot)com>, Rachel Heaton <rachelmheaton(at)gmail(dot)com>, Gareth Palmer <gareth(at)internetnz(dot)net(dot)nz>, movead li <movead(dot)li(at)highgo(dot)ca>, David Steele <david(at)pgmasters(dot)net>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Subject: Re: [PATCH] Implement INSERT SET syntax
Date: 2022-04-07 18:29:11
Message-ID: CAL9smLA9hJ-B3Eq3fxe7=CG7ESkH+C6sW762fbnVQvMxsxfVSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 23, 2022 at 5:33 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Justin Pryzby <pryzby(at)telsasoft(dot)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?

I can help with review and/or other work here. Please give me a
couple of weeks.

.m

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-04-07 18:29:44 Re: LogwrtResult contended spinlock
Previous Message Andres Freund 2022-04-07 18:12:02 Re: pgsql: Add TAP test for archive_cleanup_command and recovery_end_comman