pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonah H. Harris <jonah.harris@gmail.com>
To: Thomas Finneid <tfinneid@student.matnat.uio.no>
Cc: pgsql-performance@postgresql.org
Subject: Re: utilising multi-cpu/core machines?
Date: Wed, 5 Sep 2007 19:02:36 -0400
Message-ID: <36e682920709051602g446f538cta9dca4447c2b39fb@mail.gmail.com> (raw)
In-Reply-To: <46DF3082.7040301@ifi.uio.no>
References: <46DF3082.7040301@ifi.uio.no>

On 9/5/07, Thomas Finneid <tfinneid@student.matnat.uio.no> wrote:
> how does pg utilise multi cpus/cores, i.e. does it use more than one
> core? and possibly, how, are there any documentation about this.

Unlike other systems which manage their own affinity and
prioritization, Postgres relies solely on the OS to handle process
management across multiple CPUs/cores.

-- 
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation            | fax: 732.331.1301
33 Wood Ave S, 3rd Floor            | jharris@enterprisedb.com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/



view thread (5+ messages)  latest in thread

Message-ID: <36e682920709051602g446f538cta9dca4447c2b39fb@mail.gmail.com>
Permalink:  ../36e682920709051602g446f538cta9dca4447c2b39fb@mail.gmail.com/
Also on:    postgresql.org/message-id/36e682920709051602g446f538cta9dca4447c2b39fb@mail.gmail.com

 · 

reply

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: jonah.harris@gmail.com, tfinneid@student.matnat.uio.no
  Subject: Re: utilising multi-cpu/core machines?
  In-Reply-To: <36e682920709051602g446f538cta9dca4447c2b39fb@mail.gmail.com>

* 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