| From: | "Rick Gigger" <rick(at)alpinenetworking(dot)com> |
|---|---|
| To: | <listas(at)lozano(dot)eti(dot)br>, "Doug McNaught" <doug(at)mcnaught(dot)org> |
| Cc: | "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 21:36:28 |
| Message-ID: | 002001c3e779$1fc689b0$0700a8c0@trogdor |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory S. Williamson | 2004-01-30 21:46:33 | Re: IDENT and pg_hda.conf |
| Previous Message | Ed L. | 2004-01-30 21:33:51 | DB cache size strategies |