Re: Many instances of postgres.exe

From: Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>
To: Brian Modra <brian(at)zwartberg(dot)com>
Cc: Bob Pawley <rjpawley(at)shaw(dot)ca>, pgsql-general(at)postgresql(dot)org
Subject: Re: Many instances of postgres.exe
Date: 2009-10-15 16:12:26
Message-ID: d3ab2ec80910150912o16dd256doe2037dced061a4d5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 15, 2009 at 12:07 PM, Brian Modra <brian(at)zwartberg(dot)com> wrote:

> 2009/10/15 Bob Pawley <rjpawley(at)shaw(dot)ca>:
> > Hi
> >
> > While looking at an error message for iexplore.exe, I noticed, on Task
> > Manager, that there are 5 or more instances of postgres.exe running. Each
> > instance is consuming between 7 to 10 megs of resources, for a total of
> > almost 50 megs.
>

It's not actually using up that much memory. Windows (and linux for that
matter) think Postgres is using up that much per process, but in actuality,
most of that is shared memory between them. So if you have 5 @ 10 MB a
piece, you may only have 12 - 20 MB in use.

> >
> > Is this normal behavour?
>
> yes
>
>
+1

> > If so, could someone enlighten me as to the purpose?
>
>
>
Every time you connect to postgres, your connection gets a new
postgres.exe (plus there are a few system ones). So 5 connections = 5
postgres.exe + a few (3 or 4) system processes. It's normal, it allows the
OS to schedule who does what work. If you have multiple processors, you get
nice parallelism without postgres having to be threaded internally.

--Scott

In response to

Browse pgsql-general by date

  From Date Subject
Next Message danclemson 2009-10-15 16:31:58 npgsql and postgres enum type
Previous Message Massa, Harald Armin 2009-10-15 16:08:54 Re: Many instances of postgres.exe