After restarting PostgreSQL, I can see the following parameters are set to ON: mydb=# show stats_start_collector; stats_start_collector ----------------------- on (1 row) mydb=# show stats_start_collector; stats_start_collector ----------------------- on (1 row) mydb=# show stats_block_level; stats_block_level ------------------- on (1 row) mydb=# show stats_reset_on_server_start; stats_reset_on_server_start ----------------------------- off (1 row) But still, if I query after performing heavy DML operations, I'm always getting zero, even though there are INSERT/UPDATE/DELETE. select pg_stat_get_tuples_inserted((select oid from pg_class where relname = 'mytable')); Is there any other parameter I'm missing to make this work. -----Original Message----- From: Guillaume Lelarge [mailto:guillaume@xxxxxxxxxxxx] Sent: Wednesday, March 31, 2010 2:56 PM To: gnanam@xxxxxxxxxx Cc: pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Statistics Collector not collecting server activities Le 31/03/2010 11:14, Gnanakumar a écrit : > OK. I'll try that way. > > But, as per 8.2 doc, by default it is ON. So if I comment with just '#' > infront of the parameter, and restart PostgreSQL, this change will not be > reflected, which means it should work with default value ON? Yes, you're right. Maybe you have stats_start_collector at different places in your postgresql.conf. The last value is used in this case. So you should better check this. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin