From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | "Thomas F(dot)O'Connell" <tfo(at)sitening(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Understanding pg_autovacuum CPU Usage |
Date: | 2004-09-02 11:28:55 |
Message-ID: | 413703F7.2010503@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thomas F.O'Connell wrote:
>
> On Sep 1, 2004, at 10:27 PM, Matthew T. O'Connor wrote:
>
>> Number of rows is irrelevant, but the number of tables might not be.
>> It could be that the process of checking it's list of tables against
>> the server might be slow when used with lots of tables. Does this cpu
>> spike happen every other loop?
>
> Is there an easy way to determine if it's happening every other loop?
Yes, if you are running pg_autovacuum with a debug setting >= 1 it will
write out a message at the end of every loop.
>> Try the simple recompile with the larger update interval first and see
>> if that's the problem.
>
> How difficult would it be to make this a command-line argument if it
> turns out to be a run-time issue?
Very Easy.
From | Date | Subject | |
---|---|---|---|
Next Message | Rory Campbell-Lange | 2004-09-02 11:37:39 | search_path problem |
Previous Message | Oleg Bartunov | 2004-09-02 10:38:09 | Re: vacuum full for all databases |