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
[Charset iso-8859-1 unsupported, filtering to ASCII...]
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
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
