On Thu, Apr 05, 2007 at 01:47:03AM -0400, Tom Lane wrote:
> [ shrug... ] If the damage is already done, lazy VACUUM won't fix it.
>
Also, if there are enough open transactions at any one time and
sufficient churn in the table, lazy VACUUM may not be able to keep
up. (We had that experience with a table that was updated _very
very_ often. The answer turned out to be to update less often.
Aggregating queries that could use an index over a large number of
"expired" rows worked better than seqscans over large numbers of dead
tuples.)
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Information security isn't a technological problem. It's an economics
problem.
--Bruce Schneier
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
