Re: Controlling proliferation of postgres.exe processes

From: Alan Hodgson <ahodgson(at)reinvent(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Controlling proliferation of postgres.exe processes
Date: 2009-06-23 22:05:03
Message-ID: 200906231505.03777@hal.medialogik.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tuesday 23 June 2009, Radcon Entec <radconentec(at)yahoo(dot)com> wrote:
> Greetings!
>
> At the current moment, our customer's computer has 22 instances of
> postgres.exe running.  When a colleague checked a few minutes ago, there
> were 29.  Our contract specifies that we cannot consume more than 40% of
> the computer's memory, and we're over that level.  When does an instance
> of postgres.exe get created, and how can we make sure we create only the
> minimum number necessary?
>

Most of the memory reported in use by PostgreSQL is shared ... the actual
per-process memory use is fairly low unless your work_mem is set high and
you have queries that use it.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message raghu ram 2009-06-23 22:34:56 Error ::- “ 'more' is not recognized as an internal or external command, operable program or batch file. “
Previous Message Ivan Sergio Borgonovo 2009-06-23 21:16:53 Re: drawback of array vs join