That GUC also controls worker processes that are started by extensions, not just ones that parallel query starts. This is btw one thing I don't like at all about how the current limits work, the parallel query will fight for workers with extensions because they share the same limit.
Given that this models reality the GUC is doing its job. Now, maybe we need additional knobs to give the end-user the ability to influence how those fights will turn out.
But as far as a high-level setting goes max_worker_processes seems to fit the bill - and apparently fits within our existing cluster options naming convention.
Parallel query uses workers to assist in query execution.
