Tricking PostgreSQL into using an insane, but faster,  query plan
PostgreSQL really needs hints. Sometimes I as the developer know better than the optimizer and having to trick the optimizer to get it to do what I want is a ridiculous situation.<p>Also having the optimizer decide to do something bad off hours is not a good situation again hints or plan locking would help here.