| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: temporarily stop autovacuum |
| Date: | 2009-02-11 17:59:22 |
| Message-ID: | 1234375162.31826.104.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-02-11 at 14:21 -0300, Alvaro Herrera wrote:
> 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.
I got plenty of complaints that aren't being fixed :). pg_dump doesn't
even know how to deal with pg_autovacuum, changing scripts to handle
their autovacuum modifications won't take much.
> Hmm, argh. Maybe we do need the rule on a fake pg_autovacuum that
> Itagaki-san was proposing.
>
I don't think so. A clean cut is the way to go.
Sincerely,
Joshua D. Drake
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-02-11 18:03:54 | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
| Previous Message | Greg Stark | 2009-02-11 17:43:18 | Re: Optimization rules for semi and anti joins |