David Shadovitz wrote:

Well, now that I have the plan for my slow-running query, what do I do? Where should I focus my attention?

Briefly looking over the plan and seeing the estimated v/s actual row mismatch,I can suggest you following.

1. Vacuum(full) the database. Probably you have already done it.
2. Raise statistics_target to 500 or more and reanalyze the table(s) in question.
3. Set enable_hash_join to false, before running the query and see if it helps.



---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
     joining column's datatypes do not match

Reply via email to