Am Mittwoch, 9. Mai 2007 19:40 schrieb Tom Lane:
> Hmmm ... I see at least part of the problem, which is that email_header
> is joined twice in this query, which means that it's counted twice in
> figuring the total volume of pages competing for cache space. So the
> thing thinks cache space is oversubscribed nearly 3X when in reality
> the database is fully cached.
I should add that other, similar queries in this database that do not involve
joining the same table twice produce seemingly optimal plans. (It picks hash
joins which are actually faster than nested loops.)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
