On Fri, Jul 12, 2019 at 07:49:13AM +0200, Julien Rouhaud wrote: > It shouldn't be a problem, I reused the same infrastructure as for > vacuumdb. so run_reindex_command has a new "async" parameter, so when > there's no parallelism it's using executeMaintenanceCommand (instead > of PQsendQuery) which will block until query completion. That's why > there's no isFree usage at all in this case.
My point is more about consistency and simplification with the case where n > 1 and that we could actually move the async/sync code paths into the same banner as the async mode waits as well until a slot is free, or in short when the query completes. -- Michael
signature.asc
Description: PGP signature
