I think you are missing something. Threads and processes, to a great
extent are 6 of one and half a dozen of the other. Postgres uses
multiple processes accessing a shared memory area. A multithreaded
database would use multiple threads accessing a shared memory area. In
most OSes, threads and processes are treated very much the same way.
Threads and processes don't necessarily have to "wait". Both threads and
processes use locks. A good multi-process implementation will beat a bad
threaded one every time.
A threaded implementation can be more efficient, specifically when
you've got hundreds of simultaneous connections, but we're not talking
about some giant leap here.
That's not to say Sybase isn't faster than PostgreSQL (or slower for
that matter. I wouldn't know). But I'd advise against putting any stock
into whether it's threaded or not. As always, do your own testing.
Tiago Hermans wrote:
>
> Hi,
>
> I am really impressed with the features of PostgreSQL but am wondering if we
> should use this product for our project. We have tried several databases
> (MySQL, Sybase ASE, Sybase ASA) and we are now looking at PostgreSQL before
> releasing our service on the Internet.
>
> My concern comes from the fact that there's no multi-threading support in
> PostgreSQL and since we expect many customers to be connected at the same
> time on multiple connections, I am afraid the time to perform the SQL
> statements will be much longer, since they'll all be queued one after the
> other. Therefore, if one query takes a long time, all the other queries have
> to wait behind before being executed.
>
> Am I missing something or are my assumptions correct?
> Also, does PostgreSQL supports international characters?
>
> Thank you for any info this.
>
> Tiago Hermans
> thermans@hawaii.rr.com