X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id DDB3DD1B513 for ; Wed, 17 Sep 2003 10:49:28 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 87732-03 for ; Wed, 17 Sep 2003 07:49:20 -0300 (ADT) Received: from webbased16.localdomain (unknown [213.152.63.91]) by svr1.postgresql.org (Postfix) with ESMTP id A219CD1B50E for ; Wed, 17 Sep 2003 07:49:12 -0300 (ADT) Received: from webbased10 (firewall [213.152.63.90]) by webbased16.localdomain (8.11.6/8.11.6) with ESMTP id h8HAs3Y06213 for ; Wed, 17 Sep 2003 11:54:03 +0100 From: "Nick Barr" To: Subject: Effective Cache Size Date: Wed, 17 Sep 2003 11:48:57 +0100 Message-ID: <8F4A22E017460A458DB7BBAB65CA6AE502AA15@webbased9> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/241 X-Sequence-Number: 3607 Hi, I have been following a thread on this list "Inconsistent performance" and had a few questions especially the bits about effective_cache_size. I have read some of the docs, and some other threads on this setting, and it seems to used by the planner to either choose a sequential or index scan. So it will not necessarily increase performance I suppose but instead choose the most optimal plan. Is this correct? We are not that we are suffering massive performance issues at the moment but it is expected that our database is going to grow considerably in the next couple of years, both in terms of load and size. Also what would an appropriate setting be?