| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Carlos Oliva" <carlos(at)pbsinet(dot)com> |
| Cc: | "'Matthew T(dot) O'Connor'" <matthew(at)zeut(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance of autovacuum and full vacuum of database |
| Date: | 2005-11-11 18:55:27 |
| Message-ID: | 20662.1131735327@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Carlos Oliva" <carlos(at)pbsinet(dot)com> writes:
> Would rebooting the server interfere with the work of pg_autovacuum? I
> imagine that pg_autovacuum would loose the information that it gathered
> prior to the reboot.
The only long-term state used by autovacuum is the contents of the
statistics views, which will be saved across reboot if you have the
relevant postgresql.conf parameter set properly. (As of 8.1 it is set
to save by default, but prior releases had the opposite default :-()
At least this is true for the 8.1 integrated autovacuum, I'm less
certain about the contrib version in prior releases...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-11 19:43:10 | Re: Best way to use indexes for partial match at |
| Previous Message | Andrus | 2005-11-11 18:55:12 | Re: Best way to use indexes for partial match at |