Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Connection Limit
- From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
- To: "Jon Horsman" <horshaq(at)gmail(dot)com>
- Cc: "sql pgsql" <pgsql-sql(at)postgresql(dot)org>
- Subject: Re: Connection Limit
- Date: Mon, 30 Jul 2007 17:20:07 -0500
On 7/30/07, Jon Horsman <horshaq(at)gmail(dot)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.
- Follow-Ups:
- Re: Connection Limit
- From: Jon Horsman
- Re: Connection Limit
- References:
- Connection Limit
- From: Jon Horsman
- Connection Limit
- Prev by Date: Table-name as parameter to plpgsql
- Next by Date: Re: Table-name as parameter to plpgsql
- Previous by thread: Re: Connection Limit
- Next by thread: Re: Connection Limit
- Indexes: