Re: Commit fest 2019-09

On this CF's second week, numbers are:

      statusstring      │ week1 │ week2
────────────────────────┼───────┼───────
 Needs review           │   165 │   138
 Waiting on Author      │    30 │    44
 Ready for Committer    │    11 │     5
 Returned with Feedback │     1 │     4
 Moved to next CF       │     2 │     4
 Committed              │    14 │    23
 Rejected               │     1 │     1
 Withdrawn              │     4 │     9
(8 filas)

One of the "withdrawn" ones was a duplicate entry (2087) for a bugfix patch
(1970).

We cleared a large fraction of the patches that were waiting on
committers.  It seems that we now need people (including committers) to
focus on patches that are "Needs Review".  I marked a bunch of those as
Waiting-on-Author; patch authors have a lot of pending work.

Here's the set of patches Ready-for-Committer.  Note the majority is
pgbench-related:

 patch_id │                             name                              
──────────┼───────────────────────────────────────────────────────────────
     2217 │ pgbench - allow to create partitioned "account" tables
     2069 │ Expose queryid in pg_stat_activity in log_line_prefix
     2086 │ pgbench - extend initialization phase control
     1736 │ pgbench - add pseudo-random permutation function
     2091 │ pgbench - add \aset to store results of combined queries (\;)

I am inclined to think that 2217 is clearly something we want; 1736 is
something we probably want; and 2086 and 2091 are on the verge of being
unwanted things.

We have a number of apparently actionable bugfixes still:

 patch_id │   statusstring    │                                                            name
                                  
 

──────────┼───────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
     2224 │ Needs review      │ Race condition in logical walsender causes long postgresql shutdown delay
     2026 │ Needs review      │ Spurious "apparent wraparound" via SimpleLruTruncate() rounding (data loss)
     2179 │ Needs review      │ Fix support for hypothetical indexes using BRIN access method
     2187 │ Needs review      │ Duplicated LSN in ReorderBuffer
     2221 │ Needs review      │ Add mandatory access control for TRUNCATE
     2044 │ Needs review      │ propagating replica identity to partitions
      528 │ Needs review      │ Fix the optimization to skip WAL-logging on table created in same transaction
     2025 │ Needs review      │ SimpleLruTruncate() mutual exclusion (data loss from lack thereof)
     1995 │ Needs review      │ Replica with large recovery_min_apply_delay is not receiving changes from master after
restartuntil this delay is expired
 
     2215 │ Needs review      │ pg_upgrade fails with non-standard ACL
     2266 │ Needs review      │ Fix up partitionwise join on how equi-join conditions between the partition keys are
identified
     2050 │ Needs review      │ Fix unique join costings
     2062 │ Needs review      │ Unaccent extension python script Issue in Windows
     2205 │ Needs review      │ CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof?
     2054 │ Needs review      │ fix for BUG #3720: wrong results at using ltree

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services