| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Edoardo Ceccarelli <eddy(at)axa(dot)it>, postgres performance list <pgsql-performance(at)postgresql(dot)org>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] autovacuum on a -mostly- r/o table |
| Date: | 2006-09-27 18:33:10 |
| Message-ID: | 451AC3E6.5050108@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
Csaba Nagy wrote:
> On Wed, 2006-09-27 at 18:08, Edoardo Ceccarelli wrote:
>
>> How can I configure the vacuum to run after the daily batch insert/update?
>>
>
> Check out this:
> http://www.postgresql.org/docs/8.1/static/catalog-pg-autovacuum.html
>
> By inserting the right row you can disable autovacuum to vacuum your big
> tables, and then you can schedule vacuum nightly for those just as
> before. There's still a benefit in that you don't need to care about
> vacuuming the rest of the tables, which will be done just in time.
In addition autovacuum respects the work of manual or cron based
vacuums, so if you issue a vacuum right after a daily batch insert /
update, autovacuum won't repeat the work of that manual vacuum.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2006-09-27 19:14:02 | Re: [ADMIN] pg_hba.conf: 'trust' vs. 'md5' Issues |
| Previous Message | Lane Van Ingen | 2006-09-27 16:54:44 | Re: What Are Last Steps Performed When PostgreSQL Starts? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Schumacher | 2006-09-27 18:37:22 | Problems with inconsistant query performance. |
| Previous Message | Tobias Brox | 2006-09-27 16:53:36 | Re: autovacuum on a -mostly- r/o table |