pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Fielding <rob@dsvr.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Hang in semop() in 'waiting' backends
Date: Thu, 07 Apr 2005 00:00:04 -0400
Message-ID: <13350.1112846404@sss.pgh.pa.us> (raw)
In-Reply-To: <9daeb170ec2df50ae120e6403845e285@dsvr.net>
References: <9daeb170ec2df50ae120e6403845e285@dsvr.net>

Robert Fielding <rob@dsvr.net> writes:
> strace shows:
> semop(19529737, 0xbfffe020, 1

Can you attach to a few of the stuck processes with gdb and get stack
traces?  Are they all doing exactly the same query when they hang?

			regards, tom lane



view thread (2+ messages)

Message-ID: <13350.1112846404@sss.pgh.pa.us>
Permalink:  ../13350.1112846404@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13350.1112846404@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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, rob@dsvr.net
  Subject: Re: Hang in semop() in 'waiting' backends
  In-Reply-To: <13350.1112846404@sss.pgh.pa.us>
  References: <9daeb170ec2df50ae120e6403845e285@dsvr.net> <13350.1112846404@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