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 AB300D1BAA5 for ; Mon, 5 Apr 2004 18:11:27 +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 90570-02 for ; Mon, 5 Apr 2004 15:11:56 -0300 (ADT) Received: from gpdnet.co.uk (gpdnet.plus.com [212.56.100.243]) by svr1.postgresql.org (Postfix) with ESMTP id EC736D1BAF8 for ; Mon, 5 Apr 2004 15:11:24 -0300 (ADT) Received: from Spooler by gpdnet.co.uk (Mercury/32 v4.01a) ID MO001FDC; 5 Apr 2004 19:16:08 +0100 Received: from spooler by gpdnet.co.uk (Mercury/32 v4.01a); 5 Apr 2004 19:16:02 +0100 Received: from gary (192.168.1.2) by gpdnet.co.uk (Mercury/32 v4.01a) with ESMTP ID MG001FDB; 5 Apr 2004 19:15:53 +0100 From: "Gary Doades" To: pgsql-performance@postgresql.org Date: Mon, 05 Apr 2004 19:11:56 +0100 MIME-Version: 1.0 Subject: Re: PostgreSQL and Linux 2.6 kernel. Message-ID: <4071AF7C.15265.52B583C@localhost> In-reply-to: <200404050836.52115.josh@agliodbs.com> References: <200404040323.i343Nw3Z002747@gw.tssi.com> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/47 X-Sequence-Number: 6347 On 5 Apr 2004 at 8:36, Josh Berkus wrote: > > 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. > I agree about the "dumb" queries (I'm not mine are *that* dumb :) ) When you can write SQL that looks right, feels right, gives the right answers during testing and SQLServer runs them really fast, you stop there and tend not to tinker with the SQL further. You *can* (I certainly do) achieve comparable performance with PostgreSQL, but you just have to work harder for it. Now that I have learned the characteristics of both servers I can write SQL that is pretty good on both. I suspect that there are people who evaluate PostgreSQL by executing their favorite SQLSever queries against it, see that it is slower and never bother to go further. Cheers, Gary.