Re: PostgreSQL hanging on new connections?

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL hanging on new connections?
Date: 2010-11-29 20:57:29
Message-ID: AANLkTi=cETxGaEvAQrAajRY2GMdARpoAh5jkKCHue05j@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 29, 2010 at 1:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
>> straced postmaster when the problem was happening, and I was opening new
>> connections. strace looks like this:
>> [ backend hangs on semop immediately after reading global/pg_database ]
>
> It looks like something had exclusive lock on the database that new
> connections wanted to connect to.  AFAICS the only action in 8.3 that
> would do that would be a DROP DATABASE or RENAME DATABASE.  What was
> that other session doing?

Every once in a while when I connect to my big DB it feels like it
stalls the connection for a few seconds. I have no idea what causes
it, but it does feel like it has to do with the load. The load is not
all that high relative to what my box can handle. It doesn't happen
often enough for me to track it down, though. It instinct is that it
is waiting on a lock, but clearly there is no rename/drop happening on
my main db else i'd be out of business :-) I too run 8.3 as primary
right now... testing 9.0 for deployment soon-ish.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2010-11-29 21:01:38 Re: PostgreSQL hanging on new connections?
Previous Message Adrian Klaver 2010-11-29 20:42:29 Re: current postgresql error