| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: pg_autovacuum integration attempt #2 |
| Date: | 2004-07-17 16:05:22 |
| Message-ID: | 1090080321.91769.8.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> Exactly. However, I can work around the GUC ordering issue just by
> having the postmaster check all the required variables before launching
> autovac. What I wanted to do was have GUC prevent autovacuum = true
> when the stats collector is not enabled, reguardless of what is in
> postgresql.conf.
If the user has requested autovacuum, then why not just enable it? The
user shouldn't need to know that autovacuum is implemented via widget X
-- enable widget X for the user.
Are you also going to complain about a default statement_timeout that
doesn't allow vacuum to finish, or will you work around it by setting
statement_timeout = 0 on your connection?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-07-17 16:07:47 | Re: pg_autovacuum integration attempt #2 |
| Previous Message | Tom Lane | 2004-07-17 15:38:23 | Re: pg_autovacuum integration attempt #2 |