Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id DBD4C633700 for ; Tue, 20 Apr 2010 15:30:25 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 70432-10 for ; Tue, 20 Apr 2010 18:30:04 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gy0-f174.google.com (mail-gy0-f174.google.com [209.85.160.174]) by mail.postgresql.org (Postfix) with ESMTP id 28390632F34 for ; Tue, 20 Apr 2010 15:30:15 -0300 (ADT) Received: by gyg13 with SMTP id 13so3332466gyg.19 for ; Tue, 20 Apr 2010 11:30:14 -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:received:message-id:subject:from:to:cc:content-type; bh=+4kIFeTz3/z6SFzbiOitr3PmImICyqVKUtWLVbT/kZ0=; b=LcDzTEQko59GAri2VfSbcRstEaP+l3Bq3a/FHMtRJsz6yid86DQ+Ii/0sh4tMVsv0u rT9bIajuF32CYodAoy7RXACpf96XqFQPC7WUegpqmIIs5Fn+lmRLY8KwJuU7sK+fXFyq 0UAyIQjUytSVvTOJgPNQSonzEXQFtNd7hy64k= 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; b=GM2Gw1OsuYAu3+4SWcgR03j9r4ubx6DGA5QJ/v9KNNxwHJu0q8p5WK6gL5Ef0Imx8S aJI5wV93LxIrQd1d7YXk3Y6YaaLjX4fWVicjcCvD0Slr5Fc+dg4FzvZWk1Z5wwy/fnBW tHltvejnw2B79tdiKXNkWQYYPPNTC82F3wY+s= MIME-Version: 1.0 Received: by 10.150.218.9 with HTTP; Tue, 20 Apr 2010 11:30:14 -0700 (PDT) In-Reply-To: <20100420182832.GB53489@mr-paradox.net> References: <20100420173936.GA50886@mr-paradox.net> <20100420180351.GA51940@mr-paradox.net> <20100420182030.GA53489@mr-paradox.net> <20100420182832.GB53489@mr-paradox.net> Date: Tue, 20 Apr 2010 12:30:14 -0600 Received: by 10.150.63.21 with SMTP id l21mr7508219yba.138.1271788214349; Tue, 20 Apr 2010 11:30:14 -0700 (PDT) Message-ID: Subject: Re: Very high effective_cache_size == worse performance? From: Scott Marlowe To: David Kerr Cc: Nikolas Everett , Robert Haas , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.08 tagged_above=-10 required=5 tests=AWL=-0.180, BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201004/254 X-Sequence-Number: 38504 On Tue, Apr 20, 2010 at 12:28 PM, David Kerr wrote: > > I'm logging via syslog, I've had trouble with that before. when i moved to syslog-ng > on my dev environments that mostly resoved the probelm for me. but these machines > still have vanilla syslog. Yea, I almost always log directly via stdout on production machines because of that.