From: Scott Marlowe <scott.marlowe@gmail.com>
To: Steve Kecskes <steve@outtalimits.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Connection Limit Exceeded
Date: Tue, 9 Dec 2008 18:02:09 -0700
Message-ID: <dcc563d10812091702j1e62ec12tfd0f1a5e7076b3d7@mail.gmail.com> (raw)
In-Reply-To: <86d4d009744317fc9a45ae9065aae291@127.0.0.1>
References: <86d4d009744317fc9a45ae9065aae291@127.0.0.1>
On Tue, Dec 9, 2008 at 4:10 PM, Steve Kecskes <steve@outtalimits.com.au> wrote:
> Hi,
>
> Just wondering what actually happens when the connection limit exceeds.
>
> Dec 10 05:19:45 pallas1 postgres[373]: [2-1] FATAL: connection limit
> exceeded for non-superusers
>
> Are the requests that are rejected pooled and processed when connection
> slots are available?
Nope they're refused and you have to come back at a later time and try again.
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-admin@postgresql.org
Cc: scott.marlowe@gmail.com, steve@outtalimits.com.au
Subject: Re: Connection Limit Exceeded
In-Reply-To: <dcc563d10812091702j1e62ec12tfd0f1a5e7076b3d7@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