--JbaLeU65fPBt7QWN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thursday,  2 February 2006 at 11:25:13 +0100, Marcin Jessa wrote:
> On Thu, 2 Feb 2006 09:43:50 +0900 (JST)
> Curt Sampson <cjs@cynic.net> wrote:
>
>> On Thu, 2 Feb 2006, Marcin Jessa wrote:
>>> What threading model will be used
>>
>> PostgreSQL does not use threads; it uses a separate process for each
>> connection. So how well or poorly the OS performs with threads is
>> irrelevant.
>
> Yes, I was attenting a lecture about PostgreSQL just two days ago when
> this was mentioned and I realized that a minute after I sent this
> email...

At some level it's irrelevant.  But it would be nice to see which
approach works better for a given architecture.  In general, older
database systems use processes because at the time no good threading
systems were available.  Newer systems tend to use threads.  It would
be nice to know if this was a good choice.

Greg
--
See complete headers for address and phone numbers.

--JbaLeU65fPBt7QWN
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFD4pjkIubykFB6QiMRAqLsAJ4mOB9HgDXFIREg6CRBdB6wPFeg9ACgoM0C
GAJlEOxKkZG20LnUg/JzePI=
=fb4d
-----END PGP SIGNATURE-----

--JbaLeU65fPBt7QWN--