Skip site navigation (1) Skip section navigation (2)

Re: extra info on autovaccum log

From: Gaetano Mendola <mendola(at)bigfoot(dot)com>
To: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Subject: Re: extra info on autovaccum log
Date: 2004-07-29 16:16:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Matthew T. O'Connor wrote:

> Gaetano Mendola wrote:
>> I don't have idea about the database involved, I suggest:
>> Performing: VACUUM ANALYZE "dbame"."public"."current_connection"
>> or
>> Performing: VACUUM ANALYZE "public"."current_connection"@"dbname"
>> I know that I will know the database on the very next line, but sometimes
>> is too late :-( 
> I have thought about this before.  I didn't do it since as you say, you 
> can figure it out from looking at later log lines, but also that the log 
> line entries are already very long and will only get longer with the 
> extra info.
> BTW, I believe this will be moot in 7.5 since autovacuum will be 
> integrated into the backend and uses elog calls, so you can format the 
> log entries using GUC variables.

Well but a default line will be in the postgresql.conf, you'll insert the
dbname in the default one ?

Gaetano Mendola

In response to


pgsql-hackers by date

Next:From: Klaus NaumannDate: 2004-07-29 16:59:39
Subject: Re: Hi ...Inheritance in postgres 7.3.4 reg.
Previous:From: Bruce MomjianDate: 2004-07-29 16:14:18
Subject: Re: more signals (was: Function to kill backend)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group