On Fri, Jul 12, 2019 at 11:47 AM Julien Rouhaud <rjuju...@gmail.com> wrote: > > I didn't change the behavior wrt. possible deadlock if user specify > catalog objects using --index or --table and ask for multiple > connection, as I'm afraid that it'll add too much code for a little > benefit. Please shout if you think otherwise.
Sorry I meant schemas, not indexes. After more thinking about schema and multiple jobs, I think that erroring out is quite user unfriendly, as it's entirely ok to ask for multiple indexes and multiple object that do support parallelism in a single call. So I think it's better to remove the error, ignore the given --jobs options for indexes and document this behavior.
