| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | jd(at)commandprompt(dot)com, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: temporarily stop autovacuum |
| Date: | 2009-02-11 17:21:52 |
| Message-ID: | 20090211172152.GH8924@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> Joshua D. Drake wrote:
>> It would be a significant hack but you could update pg_autovacuum to set
>> all relations to false.
>
> Which will no longer work in 8.4.
>
> More generally, it was pointed out to me that users apparently do
> updates of pg_autovacuum to change settings on a bunch of tables at
> once. We might get some complaints if we remove that facility.
Hmm, argh. Maybe we do need the rule on a fake pg_autovacuum that
Itagaki-san was proposing.
There's a problem however; for pg_autovacuum you used to need to insert
some -1 values on columns on which you wanted to keep as defaults. On
the new code you need to skip the value altogether, and a -1 is rejected
with an error. Not sure how would we translate that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-11 17:28:32 | Re: Optimization rules for semi and anti joins |
| Previous Message | Tom Lane | 2009-02-11 17:20:37 | Re: advance local xmin more aggressively |