X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 73A21D1BA93 for ; Mon, 5 Apr 2004 15:37:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 17791-07 for ; Mon, 5 Apr 2004 12:38:14 -0300 (ADT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 1AC96D1BA90 for ; Mon, 5 Apr 2004 12:37:44 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4774963; Mon, 05 Apr 2004 08:39:40 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Mike Nolan , awerman2@hotmail.com (Aaron Werman) Subject: Re: PostgreSQL and Linux 2.6 kernel. Date: Mon, 5 Apr 2004 08:36:52 -0700 User-Agent: KMail/1.4.3 Cc: gpd@gpdnet.co.uk (Gary Doades), pgsql-performance@postgresql.org References: <200404040323.i343Nw3Z002747@gw.tssi.com> In-Reply-To: <200404040323.i343Nw3Z002747@gw.tssi.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200404050836.52115.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/36 X-Sequence-Number: 6336 Mike, > I think it is also possible that Microsoft has more programmers working > on tuning issues for SQL Server than PostgreSQL has working on the > whole project. Ah, but quantity != quality. Or they wouldn't be trolling our mailing lists trying to hire PostgreSQL programmers for the SQL Server project (really!). And we had nearly 200 contributors between 7.3 and 7.4 ... a respectable development staff for even a large corporation. Point taken, though, SQL Server has done a better job in opitimizing for "dumb" queries. This is something that PostgreSQL needs to work on, as is self-referential updates for large tables, which also tend to be really slow. Mind you, in SQL Server 7 I used to be able to crash the server with a big self-referential update, so this is a common database problem. Unfortunately, these days only Tom and Neil seem to be seriously working on the query planner (beg pardon in advance if I've missed someone) so I think the real answer is that we need another person interested in this kind of optimization before it's going to get much better. -- Josh Berkus Aglio Database Solutions San Francisco