On Thu, Aug 21, 2003 at 09:10:34PM +0530, Shridhar Daithankar wrote: > Well, nothing can help if the database has dead tuples already. > Sometime somebody has to take time to run vacuum full and/or > database reload to get a clean state.
But if you have a busy system, you'll have new dead tuples. > Point I am trying to make is to tune FSM and autovacuum frequency > such that you catch all the dead tuples in RAM, which is > non-blocking operation at the expense of some CPU power. I am sure > 1 min autovacuum I suggested is waaay too aggressive for any > scheduled vacuum isn't it? Not for some cases. In (say) 40% write situation, you have _lots_ of dead tuples. Perhaps you can make the application more efficient, but that's not always an option (maybe you don't have the code). A -- ---- Andrew Sullivan 204-4141 Yonge Street Liberty RMS Toronto, Ontario Canada <[EMAIL PROTECTED]> M2P 2A8 +1 416 646 3304 x110 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly