| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | "Nasby, Jim" <nasbyj(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru |
| Date: | 2018-09-24 20:55:41 |
| Message-ID: | 23209391537822541@iva4-6d7004ac8463.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Hi
> An autovacuum can't be just aggressive; it's either anti-wraparound or normal.
But autovacuum _can_ be aggressive and not anti-wraparound.
I build current master and can see 3 different line types:
2018-09-24 23:47:31.500 MSK 27939 @ from [vxid:4/272032 txid:0] [] LOG: automatic aggressive vacuum of table "postgres.public.foo": index scans: 0
2018-09-24 23:49:27.892 MSK 28333 @ from [vxid:4/284297 txid:0] [] LOG: automatic aggressive vacuum to prevent wraparound of table "postgres.public.foo": index scans: 0
2018-09-24 23:49:29.093 MSK 28337 @ from [vxid:4/284412 txid:0] [] LOG: automatic vacuum of table "postgres.public.foo": index scans: 0
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-09-24 21:11:17 | Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru |
| Previous Message | Andres Freund | 2018-09-24 20:45:53 | pgsql: auto_explain: Include JIT information if applicable. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-09-24 21:10:30 | Re: [PATCH] Include application_name in "connection authorized" log message |
| Previous Message | Andres Freund | 2018-09-24 20:48:00 | Re: auto_explain: Include JIT output if applicable |