Re: FW: max_connections and shared_buffers - Mailing list pgsql-admin

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?

Thanks and Regards,
Anoo S

-----Original Message-----
From: Scott Marlowe [mailto:scott.marlowe@gmail.com]
Sent: 03 September 2007 12:17
To: Anoo Sivadasan Pillai
Cc: pgsql-admin@postgresql.org
Subject: Re: FW: [ADMIN] max_connections and shared_buffers

On 9/3/07, Anoo Sivadasan Pillai <aspillai@in.rm.com> wrote:
> Hi Scott,
>
> Sorry for the long mail and Thank you for the quick response,
> My problem is that our server shuts down unexpectedly, the settings
are
> max_connections=1024,shared_buffers = 32MB for the machine. The
> following is the log snippet
> 2007-08-15 15:44:10 LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused
it.
> 2007-08-15 15:44:10 LOG:  unexpected EOF on client connection
> 2007-08-15 15:44:17 LOG:  received fast shutdown request
> 2007-08-15 15:44:17 LOG:  aborting any active transactions
> 2007-08-15 15:44:17 FATAL:  terminating connection due to
administrator
> command
> 2007-08-15 15:44:17 FATAL:  the database system is shutting down
> 2007-08-15 15:44:17 LOG:  shutting down
>
> Any clues?

Sounds like you're being hit by the Out of Memory (oom) killer in your
kernel maybe?  how many connections do you have when this happens?

I think you might need to look at connection pooling.  1024
connections is a LOT of connections.  How much memory does your server
have, btw, and what version of pgsql and what os are you running this
on?
Visit our Website at http://www.rmesi.co.in

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the
informationfor the intended purpose only. Internet communications are not secure; therefore, RMESI does not accept
legalresponsibility for the contents of this message. Any views or opinions presented are those of the author only and
notof RMESI. If this email has come to you in error, please delete it, along with any attachments. Please note that
RMESImay intercept incoming and outgoing email communications.  

Freedom of Information Act 2000
This email and any attachments may contain confidential information belonging to RMESI.  Where the email and any
attachmentsdo contain information of a confidential nature, including without limitation information relating to trade
secrets,special terms or prices these shall be deemed for the purpose of the Freedom of Information Act 2000 as
informationprovided in confidence by RMESI and the disclosure of which would be prejudicial to RMESI's commercial
interests.

This email has been scanned for viruses by Trend ScanMail.