| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Galy Lee <lee(dot)galy(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| Date: | 2007-06-07 16:18:44 |
| Message-ID: | 12511.1181233124@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> But this is misleading (started postmaster with good value, then edited
> postgresql.conf and entered "-2"):
> 17903 LOG: received SIGHUP, reloading configuration files
> 17903 LOG: -2 is outside the valid range for parameter "autovacuum_vacuum_cost_limit" (-1 .. 1000)
> Note how it still says the range is -1 .. 1000.
Can we redefine things to make zero be the "disabled" value, thus
keeping the range of valid values contiguous?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-07 16:54:03 | Re: [PATCHES] [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| Previous Message | Alvaro Herrera | 2007-06-07 15:53:36 | Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-07 16:54:03 | Re: [PATCHES] [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| Previous Message | Alvaro Herrera | 2007-06-07 15:53:36 | Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-07 16:54:03 | Re: [PATCHES] [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |
| Previous Message | Alvaro Herrera | 2007-06-07 15:53:36 | Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit |