Does the current implementation of pg_autovacuum have a way of setting windows where it is allowed to vacuum? Many large 24/7 will only allow vacuumming at certain times of the day.
Dave On Fri, 2004-04-23 at 08:58, Matthew T. O'Connor wrote: > > There are two issues here : ease-of-use for admin and basic users. > > > > On for former point, admin ease-of-use, A little story a few month ago. > > > > I succeeded in advising production people here to switch some applications > > from a mysql database, which was working perfectly, to a postgres > > database. A few weeks later, the performances were desastrous. 30 seconds > > to get an answer to a simple select on a 1500 entries tables. After > > investigation, the problems were: > > > > - no vacuum, although there were daily "DELETE FROM tables;" > > to empty all the data and reload from another source. > > > > - no analyze, because the admin did not know about it. > > My goal is to have pg_autovacuum integrated into the backend for 7.5. I > don't know if it will default to being turned on or off, I'm sure that > will be a discussion, but if it is defaulted to on, then this whole > problem of having to train newbies about vacuum should just go away. > > Matthew > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > > > > !DSPAM:40892fd393131228097780! > > -- Dave Cramer 519 939 0336 ICQ # 14675561 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
