Re: [PoC PATCH] Parallel dump to /dev/null - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PoC PATCH] Parallel dump to /dev/null
Date
Msg-id 20180301180406.amwvgmfqy7ithqgi@alap3.anarazel.de
Whole thread Raw
In response to Re: [PoC PATCH] Parallel dump to /dev/null  (Michael Banck <michael.banck@credativ.de>)
List pgsql-hackers
On 2018-03-01 14:21:24 +0100, Michael Banck wrote:
> Hi,
> 
> Am Donnerstag, den 01.03.2018, 01:28 -0800 schrieb Andres Freund:
> > Hi,
> > 
> > On 2018-02-28 14:28:41 +0100, Michael Banck wrote:
> > > I have added this patch to the next commitfest:
> > > 
> > > https://commitfest.postgresql.org/17/1576/
> > 
> > Given this is a new patch, submitted for the last commitfest, and not
> > completely trivial, I'd argue this is too late for v11.
> 
> I was under the impression that rule was rather about complicated and
> invasive patches, not just any patch which isn't completely trivial.

I think you're right this patch is a bit boderline for that. But we have
~220 pending CF entries, and fairly limited review and commit
capacity. Something's gotta give.  A lot of those are patches that have
been waiting to be committed for a while. So things added first to the
last CF the day before it starts are prime candidates.

You probably can increase your chances by herding a few patches towards
being committable.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: change in behaviour for format_type() call
Next
From: Curt Tilmes
Date:
Subject: Re: [PATCH] Find additional connection service files inpg_service.conf.d directory