From: Steve Wampler <swampler@noao.edu>
To: David Boreham <david_list@boreham.org>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Alex Turner <armtuk@gmail.com>
Cc: Luke Lonergan <LLonergan@greenplum.com>
Cc: Adam Weisberg <Aweisberg@seiu1199.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware/OS recommendations for large databases (
Date: Wed, 16 Nov 2005 07:38:52 -0700
Message-ID: <437B447C.7050508@noao.edu> (raw)
In-Reply-To: <437B43AB.7050104@boreham.org>
References: <3E37B936B592014B978C4415F90D662D01995F7B@MI8NYCMAIL06.Mi8.com>
<33c6269f0511152115v1a34ab81j30f1f5df5a6c6956@mail.gmail.com>
<437B3B18.1040509@commandprompt.com>
<437B4258.8050507@noao.edu>
<437B43AB.7050104@boreham.org>
David Boreham wrote:
> Steve Wampler wrote:
>
>> Joshua D. Drake wrote:
>>
>>
>>> The reason you want the dual core cpus is that PostgreSQL can only
>>> execute 1 query per cpu at a time,...
>>>
>>
>>
>> Is that true? I knew that PG only used one cpu per query, but how
>> does PG know how many CPUs there are to limit the number of queries?
>>
>>
>>
> He means only one query can be executing on each cpu at any particular
> instant.
Got it - the cpu is only acting on one query in any instant but may be
switching between many 'simultaneous' queries. PG isn't really involved
in the decision. That makes sense.
--
Steve Wampler -- swampler@noao.edu
The gods that smiled on your birth are now laughing out loud.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: swampler@noao.edu, david_list@boreham.org, jd@commandprompt.com, armtuk@gmail.com, LLonergan@greenplum.com, Aweisberg@seiu1199.org
Subject: Re: Hardware/OS recommendations for large databases (
In-Reply-To: <437B447C.7050508@noao.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox