Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL - Mailing list pgsql-general

From Rick Gigger
Subject Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Date
Msg-id 002001c3e779$1fc689b0$0700a8c0@trogdor
Whole thread Raw
In response to Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL  (listas@lozano.eti.br)
List pgsql-general
> > 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.

In addition I don't think that if thread A spawns thread B that thread A has
to wait until thread B terminates before it can itself terminate.  Why would
this be the case?  Threads to not necessarily have the same parent child
relationships that processes do.


pgsql-general by date:

Previous
From: "Ed L."
Date:
Subject: DB cache size strategies
Next
From: "Gregory S. Williamson"
Date:
Subject: Re: IDENT and pg_hda.conf