| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2021-09 Commitfest |
| Date: | 2021-10-02 05:30:51 |
| Message-ID: | YVfuixBDEfkq/09s@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 01, 2021 at 08:29:08PM +0200, Daniel Gustafsson wrote:
> Correct, if one looks at the activity log for an old entry the pattern of
> moving to needs review, then to the next CF, then WoA is clearly visible.
That's the tricky part. It does not really make sense either to keep
moving patches that are waiting on author for months. The scan of the
CF app I have done was about those idle patches waiting on author for
months. It takes time as authors and/or reviewers tend to sometimes
not update the status of a patch so the state in the app does not
reflect the reality, but this vacuuming limits the noise in for the
next CFs.
>> That sounds tedious!
>
> Correct.
It consumes power.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-10-02 05:40:16 | Re: Deduplicate code updating ControleFile's DBState. |
| Previous Message | Michael Paquier | 2021-10-02 05:25:44 | Re: Memory leak in pg_hmac_final |