X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3D118D1B502 for ; Sat, 4 Oct 2003 02:22:06 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 91838-08 for ; Fri, 3 Oct 2003 23:21:23 -0300 (ADT) Received: from mail.hive.nj2.inquent.com (mc.carriermail.com [205.178.180.9]) by svr1.postgresql.org (Postfix) with SMTP id B9ACFD1B513 for ; Fri, 3 Oct 2003 23:21:18 -0300 (ADT) Received: (qmail 8608 invoked from network); 4 Oct 2003 02:20:48 -0000 Received: from unknown (HELO ?192.168.1.199?) (134.22.136.235) by 205.178.180.9 with SMTP; 4 Oct 2003 02:20:48 -0000 Subject: Re: Tuning/performance issue... From: Rod Taylor To: Bruce Momjian Cc: Oleg Lebedev , Jeff , "pgsql-performance@postgresql.org" In-Reply-To: <200310040139.h941deb01679@candle.pha.pa.us> References: <200310040139.h941deb01679@candle.pha.pa.us> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-d3rx9DbM+e0D9Fq+9K2h" Message-Id: <1065234119.23288.13.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 03 Oct 2003 22:22:00 -0400 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/128 X-Sequence-Number: 3876 --=-d3rx9DbM+e0D9Fq+9K2h Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2003-10-03 at 21:39, Bruce Momjian wrote: > I have updated the FAQ to be: >=20 > In comparison to MySQL or leaner database systems, we are > faster for multiple users, complex queries, and a read/write query > load. MySQL is faster for SELECT queries done by a few users.=20 >=20 > Is this accurate? It seems so. May wish to say ... for simple SELECT queries ... Several left outer joins, subselects and a large number of joins are regularly performed faster in PostgreSQL due to a more mature optimizer. But MySQL can pump out SELECT * FROM table WHERE key =3D value; queries in a hurry. I've often wondered if they win on those because they have a lighter weight parser / optimizer with less "lets try simplifying this query" steps or if the MYISAM storage mechanism is simply quicker at pulling data off the disk. --=-d3rx9DbM+e0D9Fq+9K2h Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/fi7G6DETLow6vwwRAiilAJ46Ak9nOBg8oDvnEhE6Cp0rfTn4yACeJS8X H5493nJ6QBSbxPuCvXGkXkA= =HOEy -----END PGP SIGNATURE----- --=-d3rx9DbM+e0D9Fq+9K2h--