Interesting, this a bit of an encapsulation leak; queue management code in the in the processor implementation.  If we were going to continue to support the Monitor/PG queuing system, we should shift it to use the same ACKing framework that we added to support RabbitMQ.  Removing any mention of the 'jobs' table within the processor implementation class is the correct action.