| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Table-level log_autovacuum_min_duration |
| Date: | 2014-12-18 14:15:40 |
| Message-ID: | 20141218141540.GK1768@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier wrote:
> Hi all,
>
> Today I spent a bit of time looking at the activity of autovacuum for
> one table particularly bloated. log_autovacuum_min_duration was
> enabled and set to a high value but even with that I had to deal with
> some spam from the jobs of other tables. It would be cool to have the
> possibility to do some filtering IMO. So, what about having a relopt
> to control log_autovacuum_min_duration? RelationData->rd_options is
> largely accessible for a given relation in the code paths of vacuum
> and analyze.
+1
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-12-18 14:59:39 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Previous Message | Fujii Masao | 2014-12-18 14:08:35 | Re: Function to know last log write timestamp |