Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id F17919FB60A for ; Wed, 24 Jan 2007 16:13:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 60809-03 for ; Wed, 24 Jan 2007 16:13:25 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by postgresql.org (Postfix) with ESMTP id 1A5F59FB605 for ; Wed, 24 Jan 2007 16:13:25 -0400 (AST) Received: by locust.cns.vt.edu (Postfix, from userid 986) id 6EE0D118A24; Wed, 24 Jan 2007 15:13:24 -0500 (EST) Date: Wed, 24 Jan 2007 15:13:24 -0500 From: Ray Stell To: pgsql-admin@postgresql.org Subject: log entries in 8.2.1 Message-ID: <20070124201324.GB7143@cns.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/231 X-Sequence-Number: 24387 I get about a gazillion of these series of entries in log_filename. What will I need to trim/insert in postgresql.conf to prevent these: jira,18397,jira,2007-01-24 04:59:03.705 EST,45b68790.47dd,BEGIN LOG: duration: 0.012 ms jira,18397,jira,2007-01-24 04:59:03.705 EST,45b68790.47dd,,PARSE LOG: duration: 0.254 ms jira,18397,jira,2007-01-24 04:59:03.705 EST,45b68790.47dd,,BIND LOG: duration: 0.154 ms jira,18397,jira,2007-01-24 04:59:03.705 EST,45b68790.47dd,,SELECT LOG: duration: 0.032 ms jira,18397,jira,2007-01-24 04:59:03.706 EST,45b68790.47dd,BIND LOG: duration: 0.022 ms jira,18397,jira,2007-01-24 04:59:03.706 EST,45b68790.47dd,COMMIT LOG: duration: 0.025 ms