> As far as getting into base postgresql distro. I don't mind it rewriting but I > have some reservations. > 1) As it is postgresql source code is huge. Adding functions to it which > directly taps into it's nervous system e.g. cache, would take far more time to > perfect in all conditions.
It doesn't have to make its way into the postgresql daemon itself -- in fact since some people like tuning the vacuuming, it makes more sense to make this a daemon. No, my suggestion is simple that some sort of auto-vacuumer be compiled as a stand-alone app and included in the standard postgresql tar.gz file, and the install instructions recommend the site adding it as a cron job. On linux, it'd be good if the RPM install it automatically (or else it ran as a mostly-asleep daemon) because so many of the Linux/Postgresql users we see have just no clue about Postgresql, and no intention of reading anything. Just an FYI, a message I received today from the postmaster at a major telco about their postgresql experience: > We have experienced some problems but they have generally > cleared up after a database vacuum. However, sometimes I > have found that the vacuum itself (especially a vacuum analyze) > will go into the CPU consumption loop. -john ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
