> as for the processor, this will see an increase, of course. note,
> however, that since PostgreSQL is _not_ multithreaded, that it will run
> only on one of the processors. (i'm about to assume you are using linux
> here... 'scuse me if i'm wrong) however, the good news is that you can
> encourage linux (through the scheduler) to run postgres on one of the
> processors and everything else on the other one. this should give the
> database its own processor more oft than not. things may still drift,
> etc... but it will be better this way....
Different backends can use different CPU's, no problem.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
