On 3.12.2011 15:34, MirrorX wrote: > > but, at some point there are some bulk inserts with a different date. when > this happens and i run the query mentioned above the planner is using index > A and not index B. > i guess this happens b/c the planner due to the last analyze statistics has > no values of the new date and so it thinks that it is faster to use index A > than index B since the rows that it will search are few. but that's not the > case so this query takes much longer to finish than it would take if it used > the index B. Probably. But you haven't posted any explain plans and I've broken my crystall ball yesterday, so I can only guess. Do this: 1) get EXPLAIN ANALYZE of the query running fine 2) do the bulk update 3) get EXPLAIN ANALYZE of the query (this time it uses the wrong index) 4) run ANALYZE on the table 5) get EXPLAIN ANALYZE of the query (should be using the right index) and post the tree explain plans. > i have thought of some work-arounds to resolve this situation. for example i > could change the definition of index A to (columnA,date) and i could also > run an analyze command after every bulk insert. Another option would be to > reduce autovacuum_analyze_scale_factor to a very low value so that analyze > would be forced to be made much more often. That is not a workaround, that is a solution. The database needs reasonably accurate statistics to prepare good plans, that's how it works. If you know that the bulk insert is going to make the statistics inaccurate, you should run ANALYZE manually at the end. Or you might let autovacuum take care of that. But the autovacuum won't fix that immediately - it's running each minute or so, so the queries executed before that will see the stale stats. You may lower the autocacuum naptime, you may make it more aggressive, but that means more overhead. Tomas -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
