On Sat, Jul 21, 2012 at 4:16 PM, Ioannis Anagnostopoulos <ioan...@anatec.com> wrote: > I am not sure that I can see an improvement, at least on src_id that have > lots of msg_id per day the query never returned even 5 hours later running > "exaplain analyze". For smaller src_id > (message wise) there might be some improvement or it was just the analyse > that I run. As I said the stats goes quickly out of scope because of the big > number of updates. So it looks like that > it is not the "funny" "where" concatenation or some kind of index > construction problem. Which brings us back to the issue of the > "statistics_target" on per column. My problem is that given the > query plan I provided you yesterday, I am not sure which columns > statistics_target to touch and what short of number to introduce. Is there > any rule of thumb?
What's the size of your index, tables, and such? In GB I mean, not tuples. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
