| From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
|---|---|
| To: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Vacuum freeze |
| Date: | 2014-12-04 18:48:54 |
| Message-ID: | CAK3UJRGkOqfkMyfGiWZtDNnMua9K0wuWKSu=Hj42RccB7OuvJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Dec 4, 2014 at 12:02 PM, Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> wrote:
> check_postgres.pl (--action=autovac_freeze) recently complained that we
> needed to run VACUUM FREEZE. Doing so generated a boatload of WAL files -
> perhaps on the order of the of the database itself.
>
> Is VACUUM FREEZE something that is normally handled by autovac? If so, how
> would we approach finding what caused it not to happen automatically? Or if
> it's not, what's the normal approach to scheduling it manually to prevent
> this flood of WAL?
It is (supposed to be) handled by autovacuum: you can tune
autovacuum_freeze_max_age:
http://www.postgresql.org/docs/current/static/runtime-config-autovacuum.html
And there are similar knobs for manual VACUUMs as well.
Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-12-04 19:10:54 | Re: issue in postgresql 9.1.3 in using arrow key in Solaris platform |
| Previous Message | Vick Khera | 2014-12-04 17:26:38 | Re: Vacuum freeze |