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 5B04ED1B44A for ; Thu, 15 Jan 2004 02:48:37 +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 88818-10 for ; Wed, 14 Jan 2004 22:48:09 -0400 (AST) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id 0B90BD1B449 for ; Wed, 14 Jan 2004 22:48:04 -0400 (AST) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i0F2pn020475; Thu, 15 Jan 2004 03:51:50 +0100 Received: from bigfoot.com (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i0F2XjR26570; Thu, 15 Jan 2004 03:33:45 +0100 Message-ID: <4005FEF1.4040509@bigfoot.com> Date: Thu, 15 Jan 2004 03:46:09 +0100 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031206 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Cc: Michael Adler Subject: Re: vacuum slowed by syslogd References: <20040114031030.GA18188@pobox.com> In-Reply-To: <20040114031030.GA18188@pobox.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/128 X-Sequence-Number: 11991 Michael Adler wrote: > On many occasions, I've noticed that some PostgreSQL activity takes far longer than it previously did and that disabling syslogd addresses the symptoms. > > Most recently, it took 20-60 seconds to VACUUM a small, heavily updated table, while it used to take a fraction of a second. I found syslog entries like these: > > 13:19:53 --Relation sometable-- > 13:20:03 Removed 2 tuples in 1 pages. > 13:20:23 ^ICPU 0.00s/0.00u sec elapsed 0.00 sec. > 13:20:54 Pages 1: Changed 1, Empty 0; Tup 4: Vac 2, Keep 0, UnUsed 13. > 13:20:54 ^ITotal CPU 0.00s/0.00u sec elapsed 60.12 sec. > > It took almost-exactly 60 seconds, but virtually no CPU time was used (and no disk IO). Many similar examples have "real" times that are near perfect multiples of 10 seconds (e.g. 50.09, 40.07). This is not every single VACUUM, but it is frequent. > > The problem disappears when syslogd is stopped or when PostgreSQL disables syslog usage. This is very consistent and I can reproduce the problem in some installations by toggling these factors on and off. > Did you try to put a "-" before the file log name ? Example: LOCAL0.* -/var/log/postgresql.log Regards Gaetano Mendola