Re: Commit message / hash in commitfest page. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Commit message / hash in commitfest page.
Date
Msg-id 24637.1555421862@sss.pgh.pa.us
Whole thread Raw
In response to Re: Commit message / hash in commitfest page.  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Apr 16, 2019 at 8:55 AM Peter Eisentraut <
> peter.eisentraut@2ndquadrant.com> wrote:
>> On 2019-04-16 08:47, Magnus Hagander wrote:
>>> Unless we want to go all the way and have said bot actualy close the CF
>>> entry. But the question is, do we?

>> I don't think so.  There are too many special cases that would make this
>> unreliable, like one commit fest thread consisting of multiple patches.

> I definitely don't think we should close just because they show up.

Agreed.

> ... Which means we'd have the async/out-of-order issue.

I don't see that as much of a problem.  The use-case for these links,
as I understand it, is for retrospective examination of CF data anyway.
The mere fact of closing the CF entry is enough for real-time status.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: Compressed TOAST Slicing
Next
From: Robert Haas
Date:
Subject: Re: New vacuum option to do only freezing