| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru |
| Date: | 2018-09-14 15:35:54 |
| Message-ID: | 20180914153554.562muwr3uwujno75@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2018-Sep-13, Michael Paquier wrote:
> Improve autovacuum logging for aggressive and anti-wraparound runs
>
> A log message was being generated when log_min_duration is reached for
> autovacuum on a given relation to indicate if it was an aggressive run,
> and missed the point of mentioning if it is doing an anti-wrapround
> run. The log message generated is improved so as one, both or no extra
> details are added depending on the option set.
Hmm, can a for-wraparound vacuum really not be aggressive? I think one
of those four cases is really dead code.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-09-14 16:36:19 | pgsql: Order active window clauses for greater reuse of Sort nodes. |
| Previous Message | Tom Lane | 2018-09-14 15:22:55 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2018-09-14 15:36:43 | Re: Code of Conduct plan |
| Previous Message | Alvaro Herrera | 2018-09-14 15:29:38 | Re: when set track_commit_timestamp on, database system abort startup |