| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Amar <amarno1(at)gmail(dot)com> |
| Cc: | jaime(dot)soler(at)gmail(dot)com, Gaetano Mendola <mendola(at)gmail(dot)com>, Κοκμάδης Δημήτριος <dkokmadis(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum Running Timeframe |
| Date: | 2016-09-13 15:32:06 |
| Message-ID: | CACjxUsM5xqRisX4Z4T=gD3G2pHM0UrXg4wkHHfZZ8Rfq=5FMfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Sep 13, 2016 at 6:04 AM, Amar <amarno1(at)gmail(dot)com> wrote:
> Yes, don't disable auto vacuum.
+1
Autovacuum will have far less work to do during peak hours if you
have an off-peak-hours crontab job to run VACUUM ANALYZE. You
might want to consider doing that at the database level, run using
a database superuser login.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imre Samu | 2016-09-13 16:05:38 | Re: The sizing of HW resources of a physical PG server |
| Previous Message | Poul Kristensen | 2016-09-13 13:18:01 | Re: The sizing of HW resources of a physical PG server |