Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 501FF9FB37B for ; Fri, 12 Jan 2007 21:34:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 97283-10 for ; Fri, 12 Jan 2007 21:34:00 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [129.241.93.19]) by postgresql.org (Postfix) with ESMTP id 9B8A19FB371 for ; Fri, 12 Jan 2007 21:34:05 -0400 (AST) Received: from trofast.sesse.net ([129.241.93.32]) by cassarossa.samfundet.no with esmtp (Exim 4.50) id 1H5XmV-0002lR-2G for pgsql-performance@postgresql.org; Sat, 13 Jan 2007 02:34:03 +0100 Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1H5XmA-0000qB-00 for ; Sat, 13 Jan 2007 02:33:42 +0100 Date: Sat, 13 Jan 2007 02:33:42 +0100 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: Large table performance Message-ID: <20070113013342.GB3133@uio.no> Mail-Followup-To: pgsql-performance@postgresql.org References: <376735.48483.qm@web35309.mail.mud.yahoo.com> <87553E39-54EA-4DE4-BBEF-6FB250EDE651@fastcrypt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87553E39-54EA-4DE4-BBEF-6FB250EDE651@fastcrypt.com> X-Operating-System: Linux 2.6.19 on a x86_64 X-Message-Flag: Outlook? --> http://www.mozilla.org/products/thunderbird/ User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/211 X-Sequence-Number: 22812 On Fri, Jan 12, 2007 at 07:40:25PM -0500, Dave Cramer wrote: > 5000 is pretty low, you need at least 1/4 of memory for an 8.1.x or > newer server. Is this the new "common wisdom"? It looks like at some point, someone here said "oh, and it looks like you're better off using large values here for 8.1.x and newer", and now everybody seems to repeat it as if it was always well-known. Are there any real benchmarks out there that we can point to? And, if you set shared_buffers to half of the available memory, won't the kernel cache duplicate more or less exactly the same data? (At least that's what people used to say around here, but I guess the kernel cache gets adapted to the fact that Postgres won't ask for the most common stuff, ie. the one in the shared buffer cache.) /* Steinar */ -- Homepage: http://www.sesse.net/