| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| 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 17:26:38 |
| Message-ID: | CALd+dcf2z2Kp84FS3FS7bo8zds-edRzXpfmzpYEwQ6GmQju6kQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I don't think autovacuum can predict you will not update your table(s)
anymore, so there's no way to know to run FREEZE on it.
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?
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Kupershmidt | 2014-12-04 18:48:54 | Re: Vacuum freeze |
| Previous Message | Mike Blackwell | 2014-12-04 17:02:01 | Vacuum freeze |