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 B2AE9D1B538 for ; Thu, 30 Oct 2003 18:35:11 +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 10737-01 for ; Thu, 30 Oct 2003 14:34:40 -0400 (AST) Received: from candle.pha.pa.us (unknown [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 72D31D1B8B6 for ; Thu, 30 Oct 2003 14:34:38 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h9UIYO322264; Thu, 30 Oct 2003 13:34:24 -0500 (EST) From: Bruce Momjian Message-Id: <200310301834.h9UIYO322264@candle.pha.pa.us> Subject: Re: vacuum locking In-Reply-To: <200310301021.06719.josh@agliodbs.com> To: Josh Berkus Date: Thu, 30 Oct 2003 13:34:24 -0500 (EST) Cc: Rob Nagler , pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/770 X-Sequence-Number: 4518 Josh Berkus wrote: > > Our new project is large, high-profile, but not as data intensive as > > the problematic one. We are willing to commit significant funding and > > effort to make Postgres faster. We are "business value" driven. That > > means we solve problems practically instead of theoretically. This > > seems to be in conflict with "the Postgres way", which seems to be > > more theoretical. Our business situation comes ahead of theories. > > As always, it's a matter of balance. Our "theoretical purity" has given > PostgreSQL a reliability and recoverability level only otherwise obtainable > from Oracle for six figures. And has allowed us to build an extensibility > system that lets users define their own datatypes, operators, aggregates, > etc., in a way that is not possible on *any* other database. This is what > you're up against when you suggest changes to some of the core components ... > people don't want to break what's not broken unless there are substantial, > proven gains to be made. Let me add a little historical perspective here --- the PostgreSQL code base is almost 20 years old, and code size has doubled in the past 7 years. We are into PostgreSQL for the long haul --- that means we want code that will be working and maintainable 7 years from now. If your solution doesn't fit that case, well, you might be right, it might get rejected. However, we find that it is worth the time and effort to make our code sustainable, and it is possible your solution could be set up to do that. However, it requires you to go beyond your "business situation" logic and devote time to contribute something that will make PostgreSQL better 5 years in the future, as well as the next release. We have found very few companies that are not willing to work within that long-term perspective. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073