Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 53CDC6335BD for ; Thu, 7 Jan 2010 11:57:52 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 21380-01 for ; Thu, 7 Jan 2010 15:57:40 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mail.postgresql.org (Postfix) with ESMTP id 1E03C63297B for ; Thu, 7 Jan 2010 11:57:40 -0400 (AST) Received: by ewy26 with SMTP id 26so16790372ewy.3 for ; Thu, 07 Jan 2010 07:57:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=mE37ymfLcmisPnL1SQKDM3fst92vP7vVyjh8sIAiF3I=; b=rjpXMQ1eNPm1E9nEA+gHDYkGlKYQnxD2LdhEbnPyxkqq85HphRzOhaEQ6RAnmIQ2pt CQBEIdWiCW5bbBvjIajdCdMavCPe+LNWr+JoeoyHhQ+KsbwDsriA5T5+ggQa3Njc1iYL gBUOj/iPbKJ7eTldP077DTHAg+6ct15oTbJeQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=u5xozxcvAbufAyygwzREC+XXHbvzYxb3SvhS1+7GD/KPw6yj/sa9S8sKJGMPYejmmF 5b8V84/hlNYKdwWC7x5zA6WA3/UqZNL6vdorBB6cuQcbDkfjFZ+1g6D7RQjJPlCJklx1 PMeo8iRinQy2bI9W/QLcxprd1aRsoFDzVPL7Y= MIME-Version: 1.0 Received: by 10.216.88.21 with SMTP id z21mr1873383wee.60.1262879858130; Thu, 07 Jan 2010 07:57:38 -0800 (PST) In-Reply-To: <852badbc1001070705w45ed93d6m385ea50da2221959@mail.gmail.com> References: <852badbc1001070438j36eb10d3qa22398ffcbef405f@mail.gmail.com> <4B45E36E.4040706@tweakers.net> <852badbc1001070547p48b47175vf87efc473e3bd41b@mail.gmail.com> <26014999.20100107150535@erwied.eu> <852badbc1001070610p698dc3cfr4628b1e7768990e6@mail.gmail.com> <20100107141423.GC4315@alvh.no-ip.org> <852badbc1001070623m5d901c42k50bb808409141ca4@mail.gmail.com> <852badbc1001070705w45ed93d6m385ea50da2221959@mail.gmail.com> From: Ivan Voras Date: Thu, 7 Jan 2010 16:57:18 +0100 X-Google-Sender-Auth: 094d7c5bfa36cfd9 Message-ID: <9bbcef731001070757s61b12ac7yfbf64ca383862675@mail.gmail.com> Subject: Re: Air-traffic benchmark To: Lefteris Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=UTF-8 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.589 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FH_DATE_PAST_20XX=3.188 X-Spam-Level: X-Archive-Number: 201001/102 X-Sequence-Number: 36982 2010/1/7 Lefteris : > On Thu, Jan 7, 2010 at 3:51 PM, Ivan Voras wrote: >> On 7.1.2010 15:23, Lefteris wrote: >> >>> I think what you all said was very helpful and clear! The only part >>> that I still disagree/don't understand is the shared_buffer option:)) >> >> Did you ever try increasing shared_buffers to what was suggested (around >> 4 GB) and see what happens (I didn't see it in your posts)? > > No I did not to that yet, mainly because I need the admin of the > machine to change the shmmax of the kernel and also because I have no > multiple queries running. Does Seq scan uses shared_buffers? Everything uses shared_buffers, even things that do not benefit from it. This is because shared_buffers is the part of the general database IO - it's unavoidable.