The same thing happens to me running mod_perl with Apache
and PostgreSQL. I've kept the resources down by lowering
MinSpareServers, MaxSpareServers, and ...uh, I forget the
setting, but it's for number of clients accepted before a
child server dies (MaxClients, maybe?). But, I also
don't run a major server at this particular site.
One thing you may consider is running two apache's side
by side: one to serve mostly static documents, which you
configure ''normally'', and a second to handle your
database requests, where you set MinSpares, etc. to
values where they don't create too many postgres processes.
This is a bit of extra work, but probably worth it,
especially if you serve lots of static documents and
only a few database requests.
--Keith
[EMAIL PROTECTED]
PAUL J THOMPSON wrote:
>
> I am running Postgresql 6.5 in combination with Apache and the Apache
> JServ servlet engine. It seems that whenever I connect to the database
> from within one of my servlets, another postgres process is created that
> just sits around for a while. This is really logging down my server.
>
> After not too long I have far too many /usr/lib/postgresql/bin/postgres
> and [postmaster] processes sitting around.
>
> Does anyone know what this is happening and/or how I can stop it. I
> can't figure out whether it has something to do with me not closing the
> database connection correctly (which I believe I am) or a postgres
> configuration problem or what.
>
> Thanks,
> Paul J Thompson
