min_parallel_table_size and inheritence

The docs say:
https://www.postgresql.org/docs/current/runtime-config-query.html
|min_parallel_table_scan_size Sets the minimum amount of table data that must be scanned in order for a parallel scan
tobe considered. [...]
 

I'd like to set parallel_min_table_size=32MB, but it looks like that won't do
what I intend for at least one of our tables using inheritence.

It seems to me that an individual table should not be scanned in parallel if
its size is below the threshold, even if it's a child and has siblings which
are larger and scanned in parallel.

I found that the current behavior seems to be more or less deliberate, but
maybe should be revisited following implementation of "parallel append" node,
as previously discussed.

commit 2609e91fcf9dcf36af40cd0c5b755dccf6057df6
Author: Robert Haas <rhaas@postgresql.org>
Date:   Tue Mar 14 14:33:14 2017 -0400
|    Fix regression in parallel planning against inheritance tables.
|    
|    Commit 51ee6f3160d2e1515ed6197594bda67eb99dc2cc accidentally changed
|    the behavior around inheritance hierarchies; before, we always
|    considered parallel paths even for very small inheritance children,
|    because otherwise an inheritance hierarchy with even one small child
|    wouldn't be eligible for parallelism.  That exception was inadverently
|    removed; put it back.
[...]
|    Discussion: http://postgr.es/m/CAE9k0PmgSoOHRd60SHu09aRVTHRSs8s6pmyhJKWHxWw9C_x+XA@mail.gmail.com

postgres=# CREATE TABLE x(i int);
postgres=# CREATE TABLE x1() INHERITS(x);
postgres=# ANALYZE x,x1;
postgres=# INSERT INTO x1 SELECT * FROM generate_series(1,999999);

postgres=# SET min_parallel_table_scan_size='99MB';
postgres=# explain (COSTS OFF) SELECT * FROM x a NATURAL JOIN x b WHERE a.i<99;
| Gather
|   Workers Planned: 2
|   ->  Parallel Hash Join
|         Hash Cond: (b_1.i = a_1.i)
|         ->  Parallel Append
|               ->  Parallel Seq Scan on x1 b_1
|               ->  Parallel Seq Scan on x b
|         ->  Parallel Hash
|               ->  Parallel Append
|                     ->  Parallel Seq Scan on x1 a_1
|                           Filter: (i < 99)
|                     ->  Parallel Seq Scan on x a
|                           Filter: (i < 99)

Does parallel seq scan on table which is less than half the threshold.
| public | x1   | table | pryzbyj | 35 MB | 

Similar if x is a partitioned/relkind=p:

|postgres=# explain (COSTS OFF) SELECT * FROM x a NATURAL JOIN x b WHERE a.i<99;
| Gather
|   Workers Planned: 1
|   ->  Parallel Append
|         ->  Parallel Hash Join
|               Hash Cond: (b.i = a.i)
|               ->  Parallel Seq Scan on x1 b
|               ->  Parallel Hash
|                     ->  Parallel Seq Scan on x1 a
|                           Filter: (i < 99)

But not parallel if I join x1 directly:

postgres=# explain (COSTS OFF) SELECT * FROM x1 a NATURAL JOIN x1 b WHERE a.i<99;
| Hash Join
|   Hash Cond: (b.i = a.i)
|   ->  Seq Scan on x1 b
|   ->  Hash
|         ->  Seq Scan on x1 a
|               Filter: (i < 99)

..unless I lower threshold:

postgres=# SET min_parallel_table_scan_size='34MB';
postgres=# explain (COSTS OFF) SELECT * FROM x1 a NATURAL JOIN x1 b WHERE a.i<99;
| Gather
|   Workers Planned: 1
|   ->  Parallel Hash Join
|         Hash Cond: (b.i = a.i)
|         ->  Parallel Seq Scan on x1 b
|         ->  Parallel Hash
|               ->  Parallel Seq Scan on x1 a
|                     Filter: (i < 99)

Justin