From: Guillaume Smet <guillaume.smet@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sven Geisler <sgeisler@aeccom.com>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL and Xeon MP
Date: Thu, 16 Mar 2006 17:08:46 +0100
Message-ID: <1d4e0c10603160808y6c2f683csb74086b10c3cd40e@mail.gmail.com> (raw)
In-Reply-To: <16633.1142522409@sss.pgh.pa.us>
References: <1d4e0c10603160245n55128e86t35431a339afcf8cc@mail.gmail.com>
<44194A4B.3020106@archonet.com>
<1d4e0c10603160428s1a3c1f4cocbe8489634524387@mail.gmail.com>
<441963F4.1010607@aeccom.com>
<1d4e0c10603160630g7fe945ffo1d723843407ed128@mail.gmail.com>
<16633.1142522409@sss.pgh.pa.us>
On 3/16/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Can you try strace'ing some of the backend processes while the system is
> behaving like this? I suspect what you'll find is a whole lot of
> delaying select() calls due to high contention for spinlocks ...
Tom,
I think we can try to do it.
You mean strace -p pid with pid on some of the postgres process not on
the postmaster itself, does you? Do we need other options?
Which pattern should we expect? I'm not really familiar with strace
and its output.
Thanks for your help.
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: guillaume.smet@gmail.com, tgl@sss.pgh.pa.us, sgeisler@aeccom.com, dev@archonet.com
Subject: Re: PostgreSQL and Xeon MP
In-Reply-To: <1d4e0c10603160808y6c2f683csb74086b10c3cd40e@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