From: Scott Marlowe <scott.marlowe@gmail.com>
To: Jon Horsman <horshaq@gmail.com>
Cc: sql pgsql <pgsql-sql@postgresql.org>
Subject: Re: Connection Limit
Date: Mon, 30 Jul 2007 17:20:07 -0500
Message-ID: <dcc563d10707301520i1f561703q88427e5408b83933@mail.gmail.com> (raw)
In-Reply-To: <4f4c2a010707301429s76fb80abnf7c4a50c304647b7@mail.gmail.com>
References: <4f4c2a010707301429s76fb80abnf7c4a50c304647b7@mail.gmail.com>
On 7/30/07, Jon Horsman <horshaq@gmail.com> wrote:
> Hello,
>
> I have a server running postgres 7.4.13 and am starting to see errors
> "FATAL: connection limit exceeded for non-superusers".
>
> I'm not sure which one of my applications are hogging all of the
> connections, is there a way debug this somehow?
try netstat -an|grep 5432
assuming you're running pgsql on port 5432. The nice thing about this
trick is that since postgresql uses /tmp/.s.PGSQL.5432 for local
connections, you'll see those too.
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-sql@postgresql.org
Cc: scott.marlowe@gmail.com, horshaq@gmail.com
Subject: Re: Connection Limit
In-Reply-To: <dcc563d10707301520i1f561703q88427e5408b83933@mail.gmail.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