From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: log_autovacuum |
Date: | 2007-04-18 01:45:27 |
Message-ID: | 20070418014527.GA19186@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches pgsql-www |
Alvaro Herrera wrote:
> Seems fair. Updated patch attached.
>
> If there are no further comments, I'll add some docs and apply it later.
If autovacuum_vacuum_cost_delay is set to 20, my pitiful desktop system
takes 8.4 seconds to analyze a 8000 page table:
DEBUG: "bar": scanned 3000 of 8811 pages, containing 681000 live rows and 0 dead rows; 3000 rows in sample, 2000097 estimated total rows
LOG: automatic analyze of table "alvherre.public.bar" system usage: CPU 0.00s/0.01u sec elapsed 8.39 sec
So I guess logging on ANALYZE is not that removed from reality.
I also think we should remove these DEBUG messages, that are now
useless:
DEBUG: autovac: will ANALYZE bar
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-04-18 04:37:55 | Re: scrollable cursor support without MOVE statement |
Previous Message | FAST PostgreSQL | 2007-04-18 01:23:11 | Re: COPY-able csv log outputs |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-04-18 04:59:55 | Re: log_autovacuum |
Previous Message | Alvaro Herrera | 2007-04-17 22:57:49 | Re: log_autovacuum |