[EMAIL PROTECTED] escribió:
> Is there a way to disable some of the autovacuum logging?
Yes -- upgrade to a newer version.
Autovacuum was primitive in 8.1. It was the first version. Bear with
us.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replica
Is there a way to disable some of the autovacuum logging?
I don't want to see the below log over and over again in the logfile.
postgres[85482]: [1-1] : LOG: autovacuum: processing database
"test_com"
Thanks,
Mike
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make c
Hi, I've been trying to see whether or not autovacuum is vacuuming all
of my tables, and how often (for my peace of mind). I can see that it is
running, but I don't know what it's doing. There are a handful of key
tables in our database which suffer quite a bit if their not vacuumed
regularly (
Robert Treat wrote:
> On Thursday 27 April 2006 11:59, Bruce Momjian wrote:
> > Well, one problem now is that everytime pg_autovacuum opens a database,
> > a message is placed in the logs:
> >
> > LOG: autovacuum: processing database "test"
> > LOG: autovacuum: processing database "test"
bert Treat <[EMAIL PROTECTED]>
To: pgsql-general@postgresql.org
Cc: Bruce Momjian , "Matthew T. O'Connor"
, Will Reese <[EMAIL PROTECTED]>
Sent: Fri, 28 Apr 2006 15:15:05 -0400
Subject: Re: [GENERAL] Autovacuum Logging
> On Thursday 27 April 2006 11:59, Bruce Momjian
Robert Treat wrote:
> On Thursday 27 April 2006 11:59, Bruce Momjian wrote:
>> Well, one problem now is that everytime pg_autovacuum opens a
>> database, a message is placed in the logs:
>>
>> LOG: autovacuum: processing database "test"
>> LOG: autovacuum: processing database "test"
>>
On Thursday 27 April 2006 11:59, Bruce Momjian wrote:
> Well, one problem now is that everytime pg_autovacuum opens a database,
> a message is placed in the logs:
>
> LOG: autovacuum: processing database "test"
> LOG: autovacuum: processing database "test"
> LOG: autovacuum: pr
Well, one problem now is that everytime pg_autovacuum opens a database,
a message is placed in the logs:
LOG: autovacuum: processing database "test"
LOG: autovacuum: processing database "test"
LOG: autovacuum: processing database "test"
LOG: autovacuum:
Right, I think there has been discussion about this and general
agreement that the current autovacuum logging options are less than
ideal to put it mildly. Unfortunately, I don't think there has been any
action by anyone to do something about it. I hope to work on this at
some point, but codi
I found this short discussion between Tom and Bruce, but that's about
it for autovacuum logging.
http://archives.postgresql.org/pgsql-general/2006-04/msg00489.php
It just seems like the "processing database" log statement should be
set to a lower level, since it just logs every time autovacu
I believe 8.2 will have improved autovac logging. Take a look in the
-hackers archives for more info.
On Wed, Apr 26, 2006 at 10:47:26PM -0500, Will Reese wrote:
> Is there a reason many of the most useful autovacuum.c elog
> statements are set to DEBUG2? It seems to me that these should be
>
I found where I saw that EnterpriseDB has enabled autovacuum logging.
Look at item number one under the section entitled "Changes in
2006-03-31 update:"
http://www.enterprisedb.com/readme_dbserver.do
Will Reese -- http://blog.rezra.com
On Apr 26, 2006, at 10:47 PM, Will Reese wrote:
Is th
Is there a reason many of the most useful autovacuum.c elog
statements are set to DEBUG2? It seems to me that these should be
set to LOG.
I used autovacuum when it was a contrib module, and it failed after a
month. To prevent major performance problems I went back to the
daily vacuum.
13 matches
Mail list logo
