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 F3752D1B513 for ; Sat, 4 Oct 2003 02:50:26 +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 02633-04 for ; Fri, 3 Oct 2003 23:49:44 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id 108BBD1B54B for ; Fri, 3 Oct 2003 23:49:40 -0300 (ADT) Received: from news.hub.org (host-64-117-224-194.altec1.com [64.117.224.194] (may be forged)) by news.hub.org (8.12.9/8.12.9) with ESMTP id h942ndQj002055 for ; Sat, 4 Oct 2003 02:49:39 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h942iGuD001447 for pgsql-performance@postgresql.org; Sat, 4 Oct 2003 02:44:16 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Tuning/performance issue... Date: Fri, 03 Oct 2003 22:37:53 -0400 Organization: cbbrowne Computing Inc Lines: 39 Message-ID: References: <993DBE5B4D02194382EC8DF8554A52731D7614@postoffice.waterford.org> <200310040139.h941deb01679@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Reasonable Discussion, linux) Cancel-Lock: sha1:hJ/ot4d4IoqLrnmrtdOfHCMe5AM= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/130 X-Sequence-Number: 3878 Centuries ago, Nostradamus foresaw when pgman@candle.pha.pa.us (Bruce Momjian) would write: > I have updated the FAQ to be: > > 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. > > Is this accurate? It seems so. I would think it more accurate if you use the phrase "faster for simple SELECT queries." MySQL uses a rule-based optimizer which, when the data fits the rules well, can pump queries through lickety-split without any appreciable pause for evaluation (or reflection :-). That's _quite_ a successful strategy when users are doing what loosely amounts to evaluating association tables. select * from table where key = value; Which is just like tying a Perl variable to a hash table, and doing $value = $TABLE{$key}; In web applications where they wanted something a _little_ more structured than hash tables, that may 'hit the spot.' Anything hairier than that gets, of course, hairier. If you want something that's TRULY more structured, you may lose a lot of hair :-). -- output = reverse("gro.gultn" "@" "enworbbc") http://www.ntlug.org/~cbbrowne/oses.html "If you want to talk with some experts about something, go to the bar where they hang out, buy a round of beers, and they'll surely talk your ear off, leaving you wiser than before. If you, a stranger, show up at the bar, walk up to the table, and ask them to fax you a position paper, they'll tell you to call their office in the morning and ask for a rate sheet." -- Miguel Cruz