On Wed, 17 Sep 2003, Matt Clark wrote:

> *** THE QUESTION(S) ***
> Is there any reason for me not to run continuous sequential vacuum analyzes?
> At least for the 6 tables that see a lot of updates?
> I hear 10% of tuples updated as a good time to vac-an, but does my typical
> count of 3 indexes per table affect that?

Generally, the only time continuous vacuuming is a bad thing is when you 
are I/O bound.  If you are CPU bound, then continuous vacuuming is usually 

---------------------------(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