Re: Commitfest overflow - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Commitfest overflow
Date
Msg-id CA+hUKGJ=JQvhNy-zt3LUgJequAymdWaGXfGzZxOJ7MVNzJ7tgA@mail.gmail.com
Whole thread Raw
In response to Re: Commitfest overflow  (Greg Stark <stark@mit.edu>)
Responses Re: Commitfest overflow  (Pavel Borisov <pashkin.elfe@gmail.com>)
List pgsql-hackers
On Wed, Aug 4, 2021 at 8:23 AM Greg Stark <stark@mit.edu> wrote:
> On Tue, 3 Aug 2021 at 11:56, Bruce Momjian <bruce@momjian.us> wrote:
>
> > I wonder if our lack of in-person developer meetings is causing some of
> > our issues to not get closed.
>
> That's an interesting thought. Every year there are some especially
> contentious patches that don't get dealt with until the in-person
> meeting which pushes people to make a call. However it seems like
> that's only a handful and not really enough to explain the volume.

I think there might be a higher number of work-in-progress patches
these days, which represent ongoing collaborative efforts, and are not
expected to be committed soon, but are registered to attract the
attention of humans and robots.  Perhaps if there were a separate
status for that, it would be clearer.  Or perhaps they don't belong in
the "commit" fest.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Slow standby snapshot
Next
From: Peter Geoghegan
Date:
Subject: Re: Lowering the ever-growing heap->pd_lower