>
> AS for the process pool ... there are two camps here ... if you use
> threads, when one threads crashes the server, the server is done. With
> forking,if one backend dies, the server is still running ... in a 24x7
> shop, I'd rather the solution that doesn't die cause JoeBlow down the hall
> blew out something with his query :)
>
Due to the used shared memory I think, that this statement is not
that true for PostgreSQL ? If one backend process dies other backends
may also be killed by the postmaster ??
Marten