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 65817D1B56B for ; Wed, 13 Aug 2003 15:47:15 +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 30436-10 for ; Wed, 13 Aug 2003 12:45:38 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 13253D1B53A for ; Wed, 13 Aug 2003 12:47:04 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3509123; Wed, 13 Aug 2003 08:47:27 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Jeff , Christopher Browne Subject: Re: Perfomance Tuning Date: Wed, 13 Aug 2003 08:46:55 -0700 User-Agent: KMail/1.4.3 Cc: "pgsql-performance@postgresql.org" References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200308130846.55991.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/239 X-Sequence-Number: 3056 Jeff, > Informix, etc. have spent a lot of time and money working on it. > They also have the advantage of having many paid fulltime > developers who are doing this for a job, not as a weekend hobby > (Compared to the what? 2-3 full time PG developers). I think 4-6 full-time, actually, plus about 200 part-time contributors. Which adds up to a bloody *lot* of code if you monitor pgsql-patches between versions. The only development advantage the commercials have over us is the ability to engage in large projects (e.g. replication, raw filesystems, etc.) that are difficult for a distributed network of people. > The other advantage (which I hinted to above) with raw disks is being able > to optimize queries to take advantage of it. Informix is multithreaded > and it will spawn off multiple "readers" to do say, a seq scan (and merge > the results at the end). I like this idea. Has it ever been discussed for PostgreSQL? Hmmm .... we'd need to see some tests demonstrating that this approach was still a technical advantage given the improvements in RAID and FS technology since Informix was designed. As I have said elsewhere, Informix is probably a poor database to emulate since they are effectively an old dead-end fork of the Ingres/Postgres code, and have already been "mined" for most of the improvements they made. -- Josh Berkus Aglio Database Solutions San Francisco