From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Martín Marqués <martin(at)bugs(dot)unl(dot)edu(dot)ar> |
Cc: | pgsql-hackers(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Subject: | Re: Integrated autovacuum |
Date: | 2005-07-27 21:54:26 |
Message-ID: | 20050727215426.GK1832@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 27, 2005 at 06:35:31PM -0300, Martín Marqués wrote:
> El Mié 27 Jul 2005 18:23, Alvaro Herrera escribió:
> > On Wed, Jul 27, 2005 at 06:05:26PM -0300, Martín Marqués wrote:
> > >
> > > Will there be a way to ballance the amount of stats the autovacuum gets?
> > > Something like the analyze parameters that the contrib version has, but
> > > integrated in postgresql.conf?
> >
> > I'm not sure I understand your question. If it means what I think, then
> > yes, you can set the threshold and scale values per table.
>
> Yes, that's what I was asking. Will those values be in flat files or in the
> cataloge?[1] For what I see, it looks like flat files (presumably
> postgresql.conf)
You set cluster-wide values in postgresql.conf, and table-specific
values in the pg_autovacuum table.
Additionally you can disable autovacuum on a per-table basis.
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end." (2nd Commandment for C programmers)
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-07-27 22:00:55 | Re: wal_buffer tests in |
Previous Message | Mark Wong | 2005-07-27 21:42:01 | Re: wal_buffer tests in |