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 25FBED1B4F0 for ; Fri, 10 Oct 2003 19:21:57 +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 91494-01 for ; Fri, 10 Oct 2003 16:21:11 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id 4F584D1B52A for ; Fri, 10 Oct 2003 16:21:10 -0300 (ADT) Received: from news.hub.org (host-64-117-224-194.altec1.com [64.117.224.194] (may be forged)) by news.hub.org (8.12.9/8.12.9) with ESMTP id h9AJLAQh043684 for ; Fri, 10 Oct 2003 19:21:10 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h9AJA3DH042272 for pgsql-performance@postgresql.org; Fri, 10 Oct 2003 19:10:03 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: One or more processor ? Date: Fri, 10 Oct 2003 14:49:30 -0400 Organization: Hub.Org Networking Services Lines: 28 Message-ID: <6065ix3p39.fsf@dev6.int.libertyrms.info> References: <200310101830.49608.herve@elma.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Reasonable Discussion, linux) Cancel-Lock: sha1:kABb2qBePhvBa6AaamRgYRajKVE= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/361 X-Sequence-Number: 4109 herve@elma.fr (=?iso-8859-15?q?Herv=E9=20Piedvache?=) writes: > A simple question about PostgreSQL ... I have a Pentium Xeon Quadri processors > ... > If I do a SQL request ... does PostgreSQL use one or more processor ? Just one processor. > And if it use only one ... why ? > Could you explain me this ;o) ... Because partitioning requests across multiple processors is a hairy and difficult proposition. Some musing has been done on how threading might be used to split processing of queries across multiple CPUs, but it represents a pretty immense task involving substantial effort for design, implementation, and testing. It's tough to make this portable across all the system PostgreSQL supports, too. So while musing has been done, nobody has seriously tried implementing it. -- output = ("cbbrowne" "@" "libertyrms.info") Christopher Browne (416) 646 3304 x124 (land)