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: 410922DB.7080702@bigfoot.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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 ?

Regards
Gaetano Mendola

In response to

Responses

Browse pgsql-hackers by date

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