From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | "Alex J(dot) Avriette" <alex(at)posixnap(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum next steps |
Date: | 2004-03-23 00:49:34 |
Message-ID: | 405F899E.40407@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Matthew T. O'Connor wrote:
> Could you please explain this better, I don't really understand what the
> problem is. If you want pg_autovacuum to perform a vacuum on a table
> that has had exactly X updates no matter what, you can just run it with
> -V0 -vX (where X is the vacuum threshold) same thing can be done for
> analyze. Are you saying that you did this and it did not work as expected?
I think the problem with that (I initially tried it myself) is that
without a per-table setting, it is impractical. For instance, I want the
one large table in my app vacuumed every 500,000 dead tuples, but now my
smaller tables never reach the threshold.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-03-23 01:03:05 | Re: pg_autovacuum next steps |
Previous Message | Matthew T. O'Connor | 2004-03-23 00:42:39 | Re: pg_autovacuum next steps |