X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 6B022D1D575 for ; Wed, 14 Jan 2004 21:46:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28279-09 for ; Wed, 14 Jan 2004 17:46:21 -0400 (AST) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by svr1.postgresql.org (Postfix) with ESMTP id 73647D1B4A4 for ; Wed, 14 Jan 2004 17:46:19 -0400 (AST) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mail3.panix.com (Postfix) with ESMTP id B23619819B; Wed, 14 Jan 2004 16:46:18 -0500 (EST) Received: (from adler@localhost) by panix1.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i0ELkI402168; Wed, 14 Jan 2004 16:46:18 -0500 (EST) Date: Wed, 14 Jan 2004 16:46:18 -0500 From: Michael Adler To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: vacuum slowed by syslogd Message-ID: <20040114214618.GA26619@pobox.com> References: <20040114031030.GA18188@pobox.com> <29721.1074054979@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29721.1074054979@sss.pgh.pa.us> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/127 X-Sequence-Number: 11990 On Tue, Jan 13, 2004 at 11:36:19PM -0500, Tom Lane wrote: > Michael Adler writes: > > On many occasions, I've noticed that some PostgreSQL activity takes > > far longer than it previously did and that disabling syslogd addresses > > the symptoms. > > ... > > This evidence normally indicates a name resolution issue, but I'm not > > sure how to test for that beyond using "hostname -v -i". > > I looked in Red Hat's bugzilla for similar issues, and found a mention > that syslogd tries to reverse-lookup the address it gets each message > from. A delay there could act as you describe. At least in recent RH > releases, you can start syslogd with the "-x" switch to disable this > lookup --- does that exist in Debian, and if so does it help? There is no such option within Debian or the syslogd from freshmeat. Sounds nice, though. I was able to track down a name resolution issue. The "nameserver" in /etc/resolv.conf pointed to a nonexistent host. This added ten second delays to telnetd logins and netstat -a. This seemed to be the heart of the problem, but I'm getting some mixed info from the "field" and I'm still following up. Thanks, Mike