pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jason Coene <jcoene@gotfrag.com>
Cc: 'Mr Pink' <mr_pink_is_the_only_pro@yahoo.com>
Cc: 'Scott Kirkwood' <scottakirkwood@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Thu, 23 Sep 2004 13:05:32 -0400
Message-ID: <27437.1095959132@sss.pgh.pa.us> (raw)
In-Reply-To: <200409231653.i8NGrUaX017580@ms-smtp-02.nyroc.rr.com>
References: <200409231653.i8NGrUaX017580@ms-smtp-02.nyroc.rr.com>

"Jason Coene" <jcoene@gotfrag.com> writes:
> All of our "postgres" processes end up in the "semwai" state - seemingly
> waiting on other queries to complete.  If the system isn't taxed in CPU or
> disk, I have a good feeling that this may be the cause.

Whatever that is, I'll bet lunch that it's got 0 to do with caching
query plans.  Can you get stack tracebacks from some of the stuck
processes?  What do they show in "ps"?

			regards, tom lane



view thread (72+ messages)  latest in thread

Message-ID: <27437.1095959132@sss.pgh.pa.us>
Permalink:  ../27437.1095959132@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27437.1095959132@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, jcoene@gotfrag.com, mr_pink_is_the_only_pro@yahoo.com, scottakirkwood@gmail.com
  Subject: Re: Caching of Queries
  In-Reply-To: <27437.1095959132@sss.pgh.pa.us>

* 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