| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: log_autovacuum |
| Date: | 2007-03-08 18:31:36 |
| Message-ID: | 1173378696.3641.162.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches pgsql-www |
On Thu, 2007-03-08 at 14:53 -0300, Alvaro Herrera wrote:
> Maybe something like this is better:
>
> LOG: index passes: 1 pages: removed 0, 197 remain tuples: removed 7199, 2338 remain CPU usage: whatever
> CONTEXT: Automatic vacuuming of table "database.public.w"
Yours is better.
I've implemented this:
LOG: autovac "public.w" index passes: 1 pages: removed 0, 197 remain
tuples: removed 7199, 2338 remain CPU usage: whatever
I'm happy if this gets removed later, but I think it will help everybody
understand how multi-vacuums are working and what the best way to
specify the controls should be.
Not sure about the CONTEXT bit. I think its verbose, plus I thought that
was for ERRORs only. I will defer on this point, since I know y'all
understand that better than I.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| log_autovacuum.v2.patch | text/x-patch | 4.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-03-08 18:34:27 | Re: [PATCHES] pg_standby |
| Previous Message | Doug Knight | 2007-03-08 18:29:50 | Re: [PATCHES] pg_standby |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | NikhilS | 2007-03-09 06:29:17 | Re: log_autovacuum |
| Previous Message | Alvaro Herrera | 2007-03-08 18:13:07 | Re: log_autovacuum |