X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 87897537B6 for ; Fri, 25 Mar 2005 14:30:21 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 87653-06 for ; Fri, 25 Mar 2005 14:30:18 +0000 (GMT) Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by svr1.postgresql.org (Postfix) with ESMTP id AE9425386C for ; Fri, 25 Mar 2005 14:30:16 +0000 (GMT) Received: from demolish1 (81-6-253-170.dyn.gotadsl.co.uk [81.6.253.170]) by smtp.nildram.co.uk (Postfix) with SMTP id 2260025396E for ; Fri, 25 Mar 2005 14:30:13 +0000 (GMT) Message-ID: <000c01c53147$2c324c20$0264a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" Subject: problem with connection logging Date: Fri, 25 Mar 2005 14:30:15 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C53147.29436990" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.048 tagged_above=0 required=5 tests=AWL, HTML_50_60, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200503/416 X-Sequence-Number: 16914 This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C53147.29436990 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm running PostgreSQL 7.4.7 and have the following problem. I have "log connections" enabled in the configuration file so that I can = keep track of who's been logging on. The problem is that I also have pg_autovacuum running which logs on an = off constantly and fills up the log with its own database connections. = I'm not interested in pg_autovacuum's connections - they just clog up my = log files. Is there a way of filtering out say Unix socket or localhost connections = whilst logging all other connections? My guess is no, does anyone else suffer from this problem and if so have = you found a solution for dealing with it? thanks Donald Fraser ------=_NextPart_000_0009_01C53147.29436990 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm running PostgreSQL 7.4.7 and have = the following=20 problem.
I have "log connections" enabled in the = configuration file so that I can keep track of who's been logging=20 on.
The problem is that I also have = pg_autovacuum=20 running which logs on an off constantly and fills up the log with its = own=20 database connections. I'm not interested in pg_autovacuum's connections = - they=20 just clog up my log files.
 
Is there a way of filtering out = say Unix=20 socket or localhost connections whilst logging all=20 other connections?
 
My guess is no, does anyone else suffer = from this=20 problem and if so have you found a solution for dealing with = it?
 
thanks
Donald = Fraser
------=_NextPart_000_0009_01C53147.29436990--