58448 812 ?Ss Jul24 0:00 \_ postgres:
stats collector process
postgres 7112 1.8 1.7 2291200 570796 ?Ss 11:40 0:05 \_ postgres:
autovacuum process foundation
I don't know what autovacuum is panicking about to warrant a force run.
Any pointers ?
TIA
Dushyanth
anything else.
TIA
Dushyanth
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi,
Tom Lane tgl at sss.pgh.pa.us writes:
Dushyanth dushyanth at gmail.com writes:
Tom Lane tgl at sss.pgh.pa.us writes:
Then the only other possibility is that autovacuum is being launched to
prevent XID wraparound. Are there any tables in that database with
particularly old
Hi,
Tom Lane tgl at sss.pgh.pa.us writes:
dushy dushyanth at gmail.com writes:
On Fri, Jul 4, 2008 at 10:56 PM, Adrian Klaver aklaver at comcast.net
wrote:
One question? Did you do pg_ctl reload after changing the config file?
I did not change any config yet - autovacuum was always
Hey,
Tom Lane tgl at sss.pgh.pa.us writes:
Dushyanth dushyanth at gmail.com writes:
Does show autovacuum confirm that it's off?
Yes.
# show autovacuum;
autovacuum
off
(1 row)
Then the only other possibility is that autovacuum is being launched to
prevent
Hey all,
Iam using PostgreSQL 8.2.3 on RHEL4 (Linux 2.6.20.3-custom #4 SMP x86_64 x86_64
x86_64 GNU/Linux).
I have autovacuum tunrned off in the config, but it still seems to start up once
everyday. What could be the cause of this ?
TIA
Dushyanth
$ psql -U postgres
postgres=# show autovacuum
