Re: PostgreSQL hanging on new connections?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL hanging on new connections?
Date: 2010-11-29 18:33:53
Message-ID: 20101129183353.GB8975@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 29, 2010 at 01:23:00PM -0500, Tom Lane 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?

verified in logs. there were no alter database or drop database
statements.

Best regards,

depesz

--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: depesz(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Brar Piening 2010-11-29 20:05:41 Re: "could not accept SSPI security context"
Previous Message hubert depesz lubaczewski 2010-11-29 18:24:02 Re: PostgreSQL hanging on new connections?