Re: We need to log aborted autovacuums
От | Tom Lane |
---|---|
Тема | Re: We need to log aborted autovacuums |
Дата | |
Msg-id | 26954.1290036945@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: We need to log aborted autovacuums (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: We need to log aborted autovacuums
|
Список | pgsql-hackers |
Josh Berkus <josh@agliodbs.com> writes: >> There *is* an elog(DEBUG3) in autovacuum.c >> that reports whether autovac thinks a table needs vacuumed/analyzed ... >> maybe that needs to be a tad more user-accessible. > Yeah, it would be really good to be able to log that without bumping the > log levels of the server in general to DEBUG3. On a busy production > server, using any of the DEBUG levels is pretty much out of the question > ... they can produce up to 1GB/minute in output. Well, the way to deal with that would be to add a GUC that enables reporting of those messages at LOG level. But it's a bit hard to argue that we need such a thing without more evidence. Maybe you could just locally modify the DEBUG3 to LOG and see whether it teaches you anything? regards, tom lane
В списке pgsql-hackers по дате отправления: