New queries in 3.4(.1) result in Postgresql running 100% cpu, maas ui/api hangs

Apologies. Yes, I meant the corresponding worker process. I neglected to mention that it also seems like distribution of work to the various workers does not take into account the busy-ness of any particular worker, so hypothetically more work could be directed to this already bogged down process.