Slightly off-topic, but judging from the fact that you were able to
fix the query, it seems you have some way to modify the application
code itself. In that case, I'd try to implement caching (at least for
this statement) on the application side, for example with memcached.
--
Sent via
The fast server makes a much more accurate estimation of the number
of rows to expect (4 rows are returning, 1 was estimated). The slow
server estimates 1151 rows. Try running ANALYZE on the slow one
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to
