Re: pg 8.1.2 performance issue

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, chris smith <dmagick(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg 8.1.2 performance issue
Date: 2006-04-10 21:07:01
Message-ID: 200604102107.k3AL71D03294@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> > With our set of 4 DBs, that amounts to once every 40 minutes for
> > the given database. I see "LOG: autovacuum: processing
> > database "xyz"" in the log, but I do not see any analyze/vacuum
> > commands being issued at all (does it log when it
> > analyzes/vacuums?).
>
> Not at the default logging level --- I think you have to go to DEBUG1
> or DEBUG2 to get info about per-table actions. (This ought to be
> rethought, likely, as that will also clutter your log with a ton of
> extraneous info...)

Added to TODO:

* Allow log_min_messages to be specified on a per-module basis

This would allow administrators to see more detailed information from
specific sections of the backend, e.g. checkpoints, autovacuum, etc.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Hugo 2006-04-10 21:09:05 trigger firing order
Previous Message Florian G. Pflug 2006-04-10 20:50:14 Workaround for custom aggregate which would need "internal" as statetype