pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian Hurt <bhurt@janestcapital.com>
To: pgsql-performance@postgresql.org
To: pgsql-novice@postgresql.org
Subject: Postgres locking up?
Date: Fri, 29 Sep 2006 15:24:14 -0400
Message-ID: <451D72DE.4080205@janestcapital.com> (raw)

I'm experiencing a problem with our postgres database.  Queries that 
normally take seconds suddenly start taking hours, if they complete at 
all. 

This isn't a vacuuming or analyzing problem- I've been on this list long 
enough that they were my first response, and besides it doesn't happen 
with just a single query.    Turning off autovaccum (and switching to a 
weekend vaccuum) seems to have reduced the frequency of the problem, but 
did not eliminate it.  Besides, I've seen this problem with copy 
statements, which shouldn't be that susceptable to problems with these.

Nor is it a problem with normal database locking- when it happens, I've 
been poking around in pg_locks, and nothing seems wrong (all locks have 
been granted, no obvious deadlocks). 

Restarting the database seems to help occassionally, but not always.

This is happening both in production, where the database is held on an 
iscsi partition on an EMC, and in development, where the database is 
held on a single 7200 RPM SATA drive.  Both are Opteron-based HP 145 
servers running Centos (aka Redhat) in 64-bit mode.

What I'm looking for is pointers as to what to do next- what can I do to 
track the problem down.  Any help would be appreciated.  Thank you.

The output of pg_config:
-bash-3.00$ /usr/local/pgsql/bin/pg_config
BINDIR = /usr/local/pgsql/bin
DOCDIR = /usr/local/pgsql/doc
INCLUDEDIR = /usr/local/pgsql/include
PKGINCLUDEDIR = /usr/local/pgsql/include
INCLUDEDIR-SERVER = /usr/local/pgsql/include/server
LIBDIR = /usr/local/pgsql/lib
PKGLIBDIR = /usr/local/pgsql/lib
LOCALEDIR =
MANDIR = /usr/local/pgsql/man
SHAREDIR = /usr/local/pgsql/share
SYSCONFDIR = /usr/local/pgsql/etc
PGXS = /usr/local/pgsql/lib/pgxs/src/makefiles/pgxs.mk
CONFIGURE = '--with-perl' '--with-python' '--with-openssl' '--with-pam' 
'--enable-thread-safety'
CC = gcc
CPPFLAGS = -D_GNU_SOURCE
CFLAGS = -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline 
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing
CFLAGS_SL = -fpic
LDFLAGS = -Wl,-rpath,/usr/local/pgsql/lib
LDFLAGS_SL =
LIBS = -lpgport -lpam -lssl -lcrypto -lz -lreadline -ltermcap -lcrypt 
-lresolv -lnsl -ldl -lm -lbsd
VERSION = PostgreSQL 8.1.4
-bash-3.00$




view thread (4+ messages)  latest in thread

Message-ID: <451D72DE.4080205@janestcapital.com>
Permalink:  ../451D72DE.4080205@janestcapital.com/
Also on:    postgresql.org/message-id/451D72DE.4080205@janestcapital.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: bhurt@janestcapital.com, pgsql-novice@postgresql.org
  Subject: Re: Postgres locking up?
  In-Reply-To: <451D72DE.4080205@janestcapital.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