Tory M Blue wrote: > Any assistance would be appreciated, don't worry about slapping me > around I need to figure this out. Otherwise I'm buying new hardware > where it may not be required. What is the reporting query that takes 26 hours? You didn't seem to include it, or any query plan information for it (EXPLAIN or EXPLAIN ANALYZE results). What sort of activity is happening on the db concurrently with your tests? What's your max connection limit? What're your shared_buffers and effective_cache_size settings? Could sorts be spilling to disk? Check work_mem size and enable logging of tempfiles (see the manual). Does an explicit ANALYZE of the problem table(s) help? -- Craig Ringer -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
