Looking at the explain:
Veering aside a bit, since we usually pinpoint performance problems by looking at EXPLAIN ANALYZE's differences between the planner's estimation and actual execution's stats, what's involved in parsing the EXPLAIN ANALYZE results, and highlighting the places where they are way different? Bold, underline, or put some asterisks in front of those steps.
Makes looking at big EXPLAIN ANALYZE trees much easier.
Linux homer 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux
2:30pm up 243 days, 5:48, 8 users, load average: 5.52, 5.29, 5.10
Description: PGP signature