Re: 2018-03 CFM

Hello David,

> > Thank you for volunteering!
> >
> > I would like to be CFM assistant, if you need one :)
>
> Right now Andres and I are doing triage on the patches to determine what is
> likely to be committed in this CF.
>
> I would be very interested in your input. I generally start with patches
> that have had no email for the longest time and work my way down. You can
> sort on the "Latest Mail" column in the CF app to help.

I wrote a script that exports commitfest data into PostgreSQL. You can
find the script and the data in the attachment to this email.

Here are open CF entries ordered by Latest Mail (first 10):

select title, url, latest_mail, status
from commitfest
where not (status = 'Committed' or status = 'Rejected' or
status = 'Returned with feedback' or status = 'Moved to next CF')
order by latest_mail desc limit 10;

-[ RECORD 1 ]--------------------------------------------------------------------------
title | GUC for cleanup index threshold
url | https://commitfest.postgresql.org/17/952/
latest_mail | 2018-03-02 07:53:00
status | Needs review
-[ RECORD 2 ]--------------------------------------------------------------------------
title | Changing the autovacuum launcher scheduling; oldest table first algorithm
url | https://commitfest.postgresql.org/17/1573/
latest_mail | 2018-03-02 07:51:00
status | Needs review
-[ RECORD 3 ]--------------------------------------------------------------------------
title | Boolean partition syntax
url | https://commitfest.postgresql.org/17/1410/
latest_mail | 2018-03-02 07:49:00
status | Waiting on Author
-[ RECORD 4 ]--------------------------------------------------------------------------
title | Online enabling of checksums
url | https://commitfest.postgresql.org/17/1535/
latest_mail | 2018-03-02 07:44:00
status | Needs review
-[ RECORD 5 ]--------------------------------------------------------------------------
title | autovacuum: add possibility to change priority of vacuumed tables
url | https://commitfest.postgresql.org/17/1519/
latest_mail | 2018-03-02 07:39:00
status | Waiting on Author
-[ RECORD 6 ]--------------------------------------------------------------------------
title | Early locking option to parallel backup
url | https://commitfest.postgresql.org/17/1367/
latest_mail | 2018-03-02 07:29:00
status | Waiting on Author
-[ RECORD 7 ]--------------------------------------------------------------------------
title | log_destination=file
url | https://commitfest.postgresql.org/17/1274/
latest_mail | 2018-03-02 07:27:00
status | Needs review
-[ RECORD 8 ]--------------------------------------------------------------------------
title | chained transactions
url | https://commitfest.postgresql.org/17/1594/
latest_mail | 2018-03-02 07:18:00
status | Needs review
-[ RECORD 9 ]--------------------------------------------------------------------------
title | Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT
url | https://commitfest.postgresql.org/17/1533/
latest_mail | 2018-03-02 07:15:00
status | Needs review
-[ RECORD 10 ]-------------------------------------------------------------------------
title | kNN for SP-GiST
url | https://commitfest.postgresql.org/17/1587/
latest_mail | 2018-03-02 06:35:00
status | Needs review

However to find patches that will more likely be accepted in this CF I
believe we need to consider their status as well. For instance:

select title, url, latest_mail
from commitfest
where status = 'Ready for Committer'
and (now() - latest_mail) < interval '7 days'
order by latest_mail desc limit 10;

-[ RECORD 1 ]----------------------------------------------------------------------
title | Fix tuple count during vacuum for partial GiST indexes
url | https://commitfest.postgresql.org/17/1483/
latest_mail | 2018-03-02 05:33:00
-[ RECORD 2 ]----------------------------------------------------------------------
title | Creating backup history files for backups taken from standbys
url | https://commitfest.postgresql.org/17/1231/
latest_mail | 2018-03-02 04:14:00
-[ RECORD 3 ]----------------------------------------------------------------------
title | New function for tsquery creation
url | https://commitfest.postgresql.org/17/1202/
latest_mail | 2018-03-02 03:06:00
-[ RECORD 4 ]----------------------------------------------------------------------
title | Improve geometric types
url | https://commitfest.postgresql.org/17/1160/
latest_mail | 2018-03-02 02:45:00
-[ RECORD 5 ]----------------------------------------------------------------------
title | Mention connection parameter &quot;replication&quot; in libpq section
url | https://commitfest.postgresql.org/17/1387/
latest_mail | 2018-03-02 01:50:00
-[ RECORD 6 ]----------------------------------------------------------------------
title | MCV lists for highly skewed distributions
url | https://commitfest.postgresql.org/17/1441/
latest_mail | 2018-03-01 22:26:00
-[ RECORD 7 ]----------------------------------------------------------------------
title | Surjective indexes
url | https://commitfest.postgresql.org/17/1152/
latest_mail | 2018-03-01 19:48:00
-[ RECORD 8 ]----------------------------------------------------------------------
title | Incorrect flag passed to initial_cost_hashjoin()
url | https://commitfest.postgresql.org/17/1551/
latest_mail | 2018-03-01 19:45:00
-[ RECORD 9 ]----------------------------------------------------------------------
title | pgbench - add \if support
url | https://commitfest.postgresql.org/17/1385/
latest_mail | 2018-03-01 18:06:00
-[ RECORD 10 ]---------------------------------------------------------------------
title | Fix LWLock degradation on NUMA
url | https://commitfest.postgresql.org/17/1166/
latest_mail | 2018-03-01 15:50:00

This data is worth cross-checking with http://commitfest.cputube.org/
though. For instance, the "Improve geometric types" patch doesn't apply.
I already notified the author. I'll try to write a script that exports
data from this site as well to make cross-checking easier.

If there is anything else I can help you with, just let me know.

--
Best regards,
Aleksander Alekseev