Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 53A8263297B for ; Thu, 7 Jan 2010 12:04:02 -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 22651-04 for ; Thu, 7 Jan 2010 16:03:52 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mail.postgresql.org (Postfix) with ESMTP id 849276326D0 for ; Thu, 7 Jan 2010 12:03:51 -0400 (AST) Received: by bwz5 with SMTP id 5so11775087bwz.3 for ; Thu, 07 Jan 2010 08:03:50 -0800 (PST) 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; bh=+mfpFyVFBFS6N44VN6f4uqf5QvpmYNSWNdsT4iD6yu0=; b=KXuPlgps2gCg2ffiZeB9Ful0yRfpA4QG7d4zeI3iewbCNOj+9hZ1El1Lw6Mg7FTj1j GB+LVtV7SUX6LzEt/syyNEtzdeMrYzJfrpTGR4WikjtOaBB4Nnq3KMBTNFw+mcUN7yDy NCl4TWijFmaqkQyQXnXKEGC174+DOvMj6LUiw= 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=I47rSMIyG8rcj8Ga8EIj57KBQ3oY8bKKq3b8zbh7ppBgwa35xUb+s1KnRuKxaFsEla WqiqUMVWKSKDQqpWwTslQPzHlPcJrBe2V8wwen0g2nINMViXGXD9+4LB3RocErcfmao8 FBMs84PkhyabWxr6SuaVzEaADnK5CSOIsW/YM= MIME-Version: 1.0 Received: by 10.239.166.18 with SMTP id z18mr641501hbd.47.1262880230054; Thu, 07 Jan 2010 08:03:50 -0800 (PST) In-Reply-To: <9bbcef731001070757s61b12ac7yfbf64ca383862675@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> <9bbcef731001070757s61b12ac7yfbf64ca383862675@mail.gmail.com> Date: Thu, 7 Jan 2010 17:03:49 +0100 Message-ID: <852badbc1001070803y56d9bb23v83d8d35c1ecb4f33@mail.gmail.com> Subject: Re: Air-traffic benchmark From: Lefteris To: Ivan Voras Cc: 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=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/103 X-Sequence-Number: 36983 On Thu, Jan 7, 2010 at 4:57 PM, Ivan Voras wrote: > 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. > I will increase the shared_buffers once my kernel is configured and I will report back to you. As for the index scan, I already build an b-tree on year/month but PG (correctly) decides not to use it. The data are from year 1999 up to 2009 (my typo mistake) so it is almost 90% of the data to be accessed. When I ask for a specific year, like 2004 then the index is used and query times become faster. lefteris