| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log_autovacuum |
| Date: | 2007-08-03 17:56:59 |
| Message-ID: | 87sl70lcwk.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Actually, we happen to be running into a situation here where we need more
logging. We need to understand why autovacuum isn't considering logging this
table:
relid | schemaname | relname | seq_scan | seq_tup_read | idx_scan | idx_tup_fetch | n_tup_ins | n_tup_upd | n_tup_del | n_live_tup | n_dead_tup | last_vacuum | last_autovacuum | last_analyze | last_autoanalyze
-------+------------+------------+----------+--------------+----------+---------------+-----------+-----------+-----------+------------+------------+-------------+-------------------------------+--------------+-------------------------------
16436 | public | stock | 0 | 0 | 45929274 | 45928278 | 0 | 12116286 | 0 | 25036190 | 12723033 | | | | 2007-08-01 17:24:30.796874-07
It looks like there are some DEBUG3 messages which would be useful but I don't
know of any convenient way to change the log level in autovacuum workers.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-03 18:13:08 | "smart" shutdown is broken in HEAD |
| Previous Message | Andrew Dunstan | 2007-08-03 17:02:09 | Re: .NET driver |