Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 44BF2632AAF for ; Thu, 12 Mar 2009 04:56:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 40638-09 for ; Thu, 12 Mar 2009 04:55:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by mail.postgresql.org (Postfix) with ESMTP id 08751632C87 for ; Thu, 12 Mar 2009 04:55:35 -0300 (ADT) Received: by fxm12 with SMTP id 12so140043fxm.19 for ; Thu, 12 Mar 2009 00:55:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WgIb0BS8w7JjQh9y1DvBYrc5RG2fBHGdgBj3Hx2LrB0=; b=djf0WZ/Zom4jety49gaHROpBLk1SBkZV0hyVc8Y/rWHXrHoMZR9Rv+fAak1bJRBUZ+ qeKtgYnSjRyK0+43W/OwprMOxD3tETisgw0rc8xV8IvrM7T18W3+T2xB8ME9wRBd/aB5 /csG2DpJiJUdfyfFeyJL+WKd1s/rzkx0qHmP8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=X60pD032B7jsCfpf09CYpmG4mVj2CjR41bSkWBNTG5bvCPBUA+hhb5F9pgt2/6yqsU vAIdy8MU9E7ocSVSZxqJcjqeM4o5JSbcgb0vGnUBYPhCF3o0pOAKgdKD4tG3rUFyRcY5 1UtTzxRBS81+UkOFuFaCOg5lS8lP7lcku86Zg= MIME-Version: 1.0 Received: by 10.223.113.200 with SMTP id b8mr7039839faq.84.1236844533804; Thu, 12 Mar 2009 00:55:33 -0700 (PDT) In-Reply-To: <49B85FD9.7050406@dunslane.net> References: <7d10d2df0903111227g2e40e742g5992cba5158dd4d2@mail.gmail.com> <1d4e0c10903111659x6c96e6cau33ee121ee29a48a@mail.gmail.com> <49B85FD9.7050406@dunslane.net> Date: Thu, 12 Mar 2009 08:55:33 +0100 Message-ID: <1d4e0c10903120055p614e7d65g8a55d41faa94d346@mail.gmail.com> Subject: Re: Full statement logging problematic on larger machines? From: Guillaume Smet To: Andrew Dunstan Cc: Frank Joerdens , pgsql-performance@postgresql.org, Nic Ferrier , Avleen Vig , Mike Rogers Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/116 X-Sequence-Number: 33038 On Thu, Mar 12, 2009 at 2:05 AM, Andrew Dunstan wrote: > It is buffered at the individual log message level, so that we make sure we > don't multiplex messages. No more than that. OK. So if the OP can afford multiplexed queries by using a log analyzer supporting them, it might be a good idea to try syslog with full buffering. -- Guillaume