From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL vs. MySQL
Date: Fri, 4 Jul 2003 20:48:39 +0530
User-Agent: KMail/1.5.2
References: <20030704142800.GC4592@libertyrms.info>
	<3F05E144.10448.6784AB@localhost>
	<1057331162.40425.79.camel@jester>
In-Reply-To: <1057331162.40425.79.camel@jester>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307042048.39521.shridhar_daithankar@nospam.persistent.co.in>

On Friday 04 July 2003 20:36, Rod Taylor wrote:
> > 2. Postgresql uses shared memory being process based architecture. Mysql
> > uses process memory being threaded application. It does not need  kernel
> > settings to work and usually works best it can.
>
> MySQL has other issues with the kernel due to their threading choice
> such as memory limits per process, or poor threaded SMP support on some
> platforms (inability for a single process to use more than one CPU at a
> time regardless of thread count).
>
> Threads aren't an easy way around kernel limitations, which is probably
> why Apache has gone for a combination of the two -- but of course that
> adds complexity.

Correct. It's not debate about whether threading is better or not. But it 
certainly affects the default way with which these two applications work.

 Shridhar