Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: listas(at)lozano(dot)eti(dot)br
Cc: "Rick Gigger" <rick(at)alpinenetworking(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Randolf Richardson" <rr(at)8x(dot)ca>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Date: 2004-01-30 20:45:08
Message-ID: 87fzdxrwrv.fsf@asmodeus.mcnaught.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

listas(at)lozano(dot)eti(dot)br writes:

> I can't imagine how a web server cannot be affected by apps creating
> threads and/or proccesses. Think about memmory use, resource
> pooling, syncronization issues, ... remember a child process ot
> thread prevents the termination of its parent (which may become a
> zombie on Unix systems, and a zombie still holds its open file
> handles).

This is wrong. Parents *can* terminate with running children, and
zombie processes take up no resources other than a process table slot.

-Doug

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message listas 2004-01-30 21:00:38 Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Previous Message Rick Gigger 2004-01-30 20:32:42 Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL