From: | Ryan Mahoney <ryan(at)paymentalliance(dot)net> |
---|---|
To: | "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to run multi-processor question |
Date: | 2002-06-26 16:10:18 |
Message-ID: | 1025107818.3948.273.camel@ryan.flowlabs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Because of the multi-process design of postgresql it will automatically
take advantage of two (or more) processors if your kernel supports it.
As far as submitting to a specific process, the postmaster forks a
process for each connection, so each connection is getting a "fresh"
process and again it is up to your kernel to handle scheduling and
coordination.
-r
On Wed, 2002-06-26 at 10:01, Johnson, Shaunn wrote:
> Howdy:
>
> Running Postgres 7.1.3 on RedHat Linux 7.2 kernel 2.4.7
> on an Intel box.
>
> We are thinking about upgrading the box and adding a
> second processor. Provided that I can physically put
> a second CPU in, how can I configure Postgres to
> work with more than one proc, or better yet, submit jobs
> to the least busiest proc. What other things should I
> be aware of?
>
> Thanks!
>
> -X
From | Date | Subject | |
---|---|---|---|
Next Message | Elaine Lindelef | 2002-06-26 16:17:39 | Re: What is a tuple? |
Previous Message | Markus Wollny | 2002-06-26 15:22:14 | Re: Still problems with memory swapping and server load |