Robert Haas wrote:
> Seems like you'd also need to think about priority inversion, if the
> "low-priority" backend is holding any locks.
>
Right, that's what I was alluding to in the last part: the non-obvious
piece here is not how to decide when the backend should nap because it's
done too much I/O, it's how to figure out when it's safe for it to do so
without causing trouble for others.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.com
