X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 7166F9DC800 for ; Fri, 10 Feb 2006 17:19:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12919-02 for ; Fri, 10 Feb 2006 17:19:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.libertyrms.com (vgateway.libertyrms.info [207.219.45.62]) by postgresql.org (Postfix) with ESMTP id 857F09DC826 for ; Fri, 10 Feb 2006 17:19:36 -0400 (AST) Received: from dba5.int.libertyrms.com ([10.1.3.44]) by mail.libertyrms.com with esmtp (Exim 4.22) id 1F7fg1-0000mv-J4; Fri, 10 Feb 2006 16:19:37 -0500 Message-ID: <43ED0369.2090705@ca.afilias.info> Date: Fri, 10 Feb 2006 16:19:37 -0500 From: Brad Nicholson User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "C. Bensend" CC: pgsql-admin@postgresql.org Subject: Re: Is the database being VACUUMed? References: <2894.134.244.169.17.1139587037.squirrel@webmail.stinkweasel.net> <6064nneznu.fsf@dba2.int.libertyrms.com> <4131.134.244.169.17.1139606011.squirrel@webmail.stinkweasel.net> In-Reply-To: <4131.134.244.169.17.1139606011.squirrel@webmail.stinkweasel.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Mail-From: bnichols@ca.afilias.info X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.226 required=5 tests=[AWL=0.226] X-Spam-Score: 0.226 X-Spam-Level: X-Archive-Number: 200602/115 X-Sequence-Number: 20536 C. Bensend wrote: >>If you have command string monitoring turned on, via >>stats_command_string in the postgresql.conf file, then you could get >>this information from the system view pg_stat_activity. >> >>Generally, you could look to see if a current_query is a vacuum, perhaps >>via... >> >>select * from pg_stat_activity where lower(current_query) like 'vacuum%' ; >> >> > >Are there any drawbacks to turning this on (mine is not)? If not, >I can certainly do that. > > > Well, you have to turn on the stats collector, so you will pay a little bit of a performance penalty for that. I doubt you'll notice it unless you're really close to the edge. You do have to restart the database to enable the stats collector if it's off. The pg_stat_activity stuff is pretty essential for debugging problems in the database. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.