Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 68A0864FD1B for ; Fri, 19 Sep 2008 10:52:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 40943-07 for ; Fri, 19 Sep 2008 10:52:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id 32C5C64FD05 for ; Fri, 19 Sep 2008 10:52:35 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Fri, 19 Sep 2008 08:52:33 -0500 Message-Id: <48D36842.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.3 Date: Fri, 19 Sep 2008 08:52:18 -0500 From: "Kevin Grittner" To: "c k" , Subject: Re: Multi-processors References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200809/215 X-Sequence-Number: 30308 >>> "c k" wrote: > Does PG uses multiple processors/cores if available by default on various > OSes? A separate process is created to handle each connection. You don't get much benefit from multiple processors if only one connection at a time is running a query, but in a normal mix it uses all processors. > What are the limitations on using multiple processors/cores and main > memory? I'm not sure what you're getting at here, but PostgreSQL goes through the file system, so OS caching (which is what usually happens to otherwise unused system RAM) benefits PostgreSQL. Does that help? -Kevin