X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 82F6A9FA159 for ; Wed, 6 Sep 2006 07:38:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 17003-09 for ; Wed, 6 Sep 2006 07:38:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 1588D9FA0FC for ; Wed, 6 Sep 2006 07:38:43 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from alimail.net (potatis.alimail.net [84.19.131.11]) by svr4.postgresql.org (Postfix) with ESMTP id E758F5AF889 for ; Wed, 6 Sep 2006 10:38:41 +0000 (GMT) Received: from [192.168.1.10] ([84.19.128.181]) by alimail.net (alimail.net [10.1.8.71]) (MDaemon.PRO.v8.0.4.R) with ESMTP id md50000761767.msg for ; Wed, 06 Sep 2006 12:37:36 +0200 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: Niklas Johansson Subject: Re: How to check if VACUUM operations are working? Date: Wed, 6 Sep 2006 12:37:34 +0200 To: Miguel Arroz X-Mailer: Apple Mail (2.752.2) X-Spam-Processed: alimail.net, Wed, 06 Sep 2006 12:37:36 +0200 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 84.19.128.181 X-Return-Path: spot@tele2.se X-MDaemon-Deliver-To: pgsql-admin@postgresql.org Reply-To: spot@tele2.se X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/33 X-Sequence-Number: 22947 On 6 sep 2006, at 01.07, Miguel Arroz wrote: > I have PgSQL 8.0.* installed on a Mac OS X Server machine. > > I setup a LaunchDeamon to run a vacuum command every night. The > problem is that LaunchDeamon still lacks some features, one of them > is logging... so, I'm not entirely sure if the vacuum operations > actually runs. You can add the key 'StandardOutPath' to your launchd.plist file: StandardOutPath /path/to/logfile You can also supply 'StandardErrorPath'. This of course only works for commands that writes information to stdout (or stderr). If not, or if the output is not directly suitable for logging, it might be necessary to wrap the command in a script in order to generate additional logging information, e.g. timestamp. Sincerely, Niklas Johansson