public inbox for [email protected]  

help / color / mirror / Atom feed

From: NikhilS <[email protected]>
To: Simon Riggs <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: [email protected]
Subject: Re: log_autovacuum
Date: Fri, 9 Mar 2007 11:59:17 +0530
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Hi,

On 3/9/07, Simon Riggs <[email protected]> wrote:
>
> 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.


IMHO, it would be good to have both the messages spit out. The earlier
message is much better for parsing and the later makes READABLE sense.

Regards,
Nikhils

-- 
EnterpriseDB               http://www.enterprisedb.com

view thread (29+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: log_autovacuum
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox