Re: What is the practical limitation of no multi-threading?

> Not being multithreaded may only be a big deal if your application connects
> and disconnects from the database at high rates. In that situation, such an
> application would suffer the poorer performance of multiprocess servers like
> Postgres since it is significantly more time consuming to copy the memory
> management unit (mmu) state, or at least to load a new program image (the
> backend), than with threads which share mmu state and program image.

Let me mention that we don't load new executables on backend startup.
We merely fork() the postmaster. I just checked the FAQ and it seems
pretty clear. Please let me know if there is additional info I should
have there.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026