From: Scott Marlowe <scott.marlowe@gmail.com>
To: Anoo Sivadasan Pillai <aspillai@in.rm.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: FW: max_connections and shared_buffers
Date: Mon, 3 Sep 2007 02:28:11 -0500
Message-ID: <dcc563d10709030028s3ec40330lc6beb2256c7279a6@mail.gmail.com> (raw)
In-Reply-To: <772CDA49C515244FA14E34443F62E56402F17455@EX-INDIA1.internal.rmplc.net>
References: <772CDA49C515244FA14E34443F62E56402F173E0@EX-INDIA1.internal.rmplc.net>
<dcc563d10709022347j19305a58q9c9a2dc987768e5@mail.gmail.com>
<772CDA49C515244FA14E34443F62E56402F17455@EX-INDIA1.internal.rmplc.net>
On 9/3/07, Anoo Sivadasan Pillai <aspillai@in.rm.com> wrote:
> Hi Scott,
> We will be putting connection pooling, But as of now we have to find
> some cure before implementing pooling.
>
> Memory - 2GB
> Postgres - PostgreSQL 8.2.4
> OS - Windows 2003 server installation: ( Service
> Pack 2 )
>
> I am not sure how to get the number of connections while this happens.
> How this can be taken?
Not sure with Windows. I'm strictly a unix type of guy. I'm guessing
that Windows is detecting too many connections / out of memory and
shutting down the service.
Is there anything in the system logs that might give you a hint of why
pgsql is being shut down by the OS?
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, aspillai@in.rm.com
Subject: Re: FW: max_connections and shared_buffers
In-Reply-To: <dcc563d10709030028s3ec40330lc6beb2256c7279a6@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