pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wayne Piekarski <wayne@senet.com.au>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Re: INSERT/UPDATE waiting (another example)
Date: Thu, 06 May 1999 10:04:56 -0400
Message-ID: <8733.925999496@sss.pgh.pa.us> (raw)
In-Reply-To: <199905060331.NAA26678@helpdesk.senet.com.au>

Wayne Piekarski <wayne@senet.com.au> writes:
> We are experiencing exactly the same problem as above - during the day,
> all of a sudden Postgres will completely jam up, with all processing in
> one of the following states: (from ps -axwwwwww)

It seems possible that the hashtable bugs I fixed a couple months ago
are rising up to bite you.  (Basically, the shared hashtables that
contain things like locks and buffers would go nuts if there got to be
more than 256 entries ... and it sure sounds like your installation is
big enough that it could have, eg, more than 256 active locks when
under load.)  One quick thing you might try to test this is to reduce
the postmaster's -B setting to less than 256 (if you have it set that
high) and see if stability improves.

These bugs are fixed in 6.5-beta1, but it has enough other bugs that
I don't think Wayne would be wise to try moving to 6.5 just yet.
I have a patch for 6.4.2 that I believe also fixes the problems, but
it hasn't gotten quite as much testing as I would like so I haven't
committed it into the REL6_4 tree.  (There's not going to be a 6.4.3
release, according to current plans, so it's hardly worth doing anyway.)

What I will do is send the patch to Wayne in a separate message, and
also cc: it to the PATCHES list --- anyone else who needs it can get it
from there.  Please let us know if this helps, Wayne.

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <8733.925999496@sss.pgh.pa.us>
Permalink:  ../8733.925999496@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8733.925999496@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-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, wayne@senet.com.au, pgsql-hackers@postgreSQL.org
  Subject: Re: [HACKERS] Re: INSERT/UPDATE waiting (another example)
  In-Reply-To: <8733.925999496@sss.pgh.pa.us>
  References: <199905060331.NAA26678@helpdesk.senet.com.au> <8733.925999496@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