X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CD4F8D1BB5F; Wed, 10 Mar 2004 01:09:16 +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 26384-04; Tue, 9 Mar 2004 21:09:16 -0400 (AST) Received: from bucky.ehpg.net (mail.ehpg.net [64.71.189.194]) by svr1.postgresql.org (Postfix) with ESMTP id 21956D1BA93; Tue, 9 Mar 2004 21:09:13 -0400 (AST) Received: from (ehpg.net) [208.29.195.71]by bucky.ehpg.netwith asmtp(Exim 4.21 #1 (Gentoo Linux 1.4))id 1B0sDj-0003x7-WE; Tue, 09 Mar 2004 17:09:16 -0800 Message-ID: <404E6AB9.4030404@ehpg.net> Date: Tue, 09 Mar 2004 17:09:13 -0800 From: "Gavin M. Roy" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: PgSQL Performance ML , Postgres Admin List Subject: Re: [PERFORM] syslog slowing the database? References: <404E2937.4060604@cranel.com> <370.1078877805@sss.pgh.pa.us> In-Reply-To: <370.1078877805@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanned: Clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/174 X-Sequence-Number: 12743 Might want to look at metalog, it does delayed writes, though ultimately your issue is io bound and there's not much you can do to reduce io if you want to keep syslog logging your pgsql queries and such. Tom Lane wrote: >Greg Spiegelberg writes: > > >>I turned syslog back on and the restore slowed down again. Turned >>it off and it sped right back up. >> >> > >We have heard reports before of syslog being quite slow. What platform >are you on exactly? Does Richard's suggestion of turning off syslog's >fsync help? > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > >