| From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Autovacuum launcher doesn't notice death of postmaster immediately |
| Date: | 2007-06-07 15:50:36 |
| Message-ID: | 20070607155036.GH92628@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, Jun 04, 2007 at 11:04:26AM -0400, Alvaro Herrera wrote:
> The launcher is set up to wake up in autovacuum_naptime seconds at most.
> So if the user configures a ridiculuos time (for example 86400 seconds,
> which I've seen) then the launcher would not detect the postmaster death
Yeah, I've seen people set that up with the intention of "now autovacuum
will only run during our slow time!". I'm thinking it'd be worth
mentioning in the docs that this won't work, and instead suggesting that
they run vacuumdb -a or equivalent at that time instead. Thoughts?
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-07 15:53:36 | Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| Previous Message | Tom Lane | 2007-06-07 15:44:15 | Re: [COMMITTERS] pgsql: Create a GUC parametertemp_tablespacesthat allows selection of |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-07 15:53:36 | Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| Previous Message | Tom Lane | 2007-06-07 14:16:25 | Re: Controlling Load Distributed Checkpoints |