Thread: Too many postgres.exe

On 15/12/2009 5:51 PM, A.Bhattacharya@sungard.com wrote:

> However whenever my application is running I could see there are too
> many postgres.exe are created even though the application is not doing
> anything in database.

What is "too many" ?

What does:

   SELECT * FROM pg_stat_activity;

show?

How are you talking to PostgreSQL? Direct JDBC? An ORM like Hibernate?
Which one? What JDBC driver version? Are you using a connection pool?
Which one?

The people on this mailing list are, with the possible exception of Tom,
not psychic. Some kind of details will help your question get a better
answer, more quickly. See:

   http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

> In general the observation is that there are too many progress.exe
> processes get created every time I run my application and it
> postgres.exe eats up the maximum memory.

Then your server is not configured correctly. Set max connections,
shared_buffers, work_mem, maintenance_work_mem, etc so that your server
cannot consume too much memory.

--
Craig Ringer

A.Bhattacharya@sungard.com, 15.12.2009 10:51:
> Hi All,
>
> I have my application UI in Java and which is communicating with
> Postgresql database.
>
> However whenever my application is running I could see there are too
> many postgres.exe are created even though the application is not doing
> anything in database.
>
> In general the observation is that there are too many progress.exe
> processes get created every time I run my application and it
> postgres.exe eats up the maximum memory.

Define "too many".

Each connection that you open will start up a new postgres.exe

As Craig has already pointed out you have not specified enough details, so people can only guess what is going wrong
(ifat all) 

My best guess is:

- you are simply not closing your connections when you are don
- you have configured a connection pool that creates a high number of initial connections

Thomas

A.Bhattacharya@sungard.com wrote:
>
> Hi All,
>
>
>
> I have my application UI in Java and which is communicating with
> Postgresql database.
>
> However whenever my application is running I could see there are too
> many postgres.exe are created even though the application is not doing
> anything in database.
>
>
>
Have you defined a connection pool? It is possible that the connections
are part of a pool and will be created when your application starts. You
should be able to change the minimum/maximum pool size.

Howard
www.selestial.com