| From: | Steve Wampler <swampler(at)noao(dot)edu> |
|---|---|
| To: | David Boreham <david_list(at)boreham(dot)org> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Alex Turner <armtuk(at)gmail(dot)com>, Luke Lonergan <LLonergan(at)greenplum(dot)com>, Adam Weisberg <Aweisberg(at)seiu1199(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Hardware/OS recommendations for large databases ( |
| Date: | 2005-11-16 14:38:52 |
| Message-ID: | 437B447C.7050508@noao.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)noao(dot)edu
The gods that smiled on your birth are now laughing out loud.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Boreham | 2005-11-16 14:51:31 | Re: Hardware/OS recommendations for large databases ( |
| Previous Message | William Yu | 2005-11-16 14:37:48 | Re: Hardware/OS recommendations for large databases ( |