| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: extra info on autovaccum log |
| Date: | 2004-07-29 15:21:29 |
| Message-ID: | 410915F9.90902@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Matthew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-07-29 16:14:18 | Re: more signals (was: Function to kill backend) |
| Previous Message | Thomas Hallgren | 2004-07-29 14:56:44 | Re: Sketch of extending error handling for subtransactions in functions |