Re: Postgres 8.0 windows processes, field testing, and

From: Alvaro Herrera <alvherre(at)surnet(dot)cl>
To: Joe <svn(at)freedomcircle(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres 8.0 windows processes, field testing, and
Date: 2005-06-24 20:17:41
Message-ID: 20050624201741.GC9586@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jun 24, 2005 at 04:00:36PM -0400, Joe wrote:
> Richard Huxton wrote:
>
> > You will have (assuming the same as on *nix):
> > 1. Master process - starts all the others
> > 2. One backend per client
> > 3. Stats buffer/collector
> > 4. Auto-vacuum (optional, not really part of the main system yet)
>
>
> It appears that, when started as a Windows service, four backend processes
> (postgres.exe) are started even though there are no clients yet.

They likely belong to the stats collector process, the stats buffer
process, the background writer process, and one postmaster to rule them
all. They are all launched from the same postgres.exe executable.

> Is this simply to avoid backend process creation time for the first
> few clients?

No, we don't do that.

> Out of curiosity, is this approach also used on *nix?

Yes.

> A pg_ctl.exe is also running. I presume that is the one that starts the
> postmaster and then sits and waits for a signal to shutdown the service?

Probably.

--
Alvaro Herrera (<alvherre[a]surnet.cl>)
Jude: I wish humans laid eggs
Ringlord: Why would you want humans to lay eggs?
Jude: So I can eat them

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-06-24 21:33:12 Re: Postmaster Out of Memory
Previous Message Tom Lane 2005-06-24 20:16:26 Re: Postmaster Out of Memory