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 0EBEED1B4F1 for ; Thu, 30 Oct 2003 00:58:00 +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 35832-10 for ; Wed, 29 Oct 2003 20:57:32 -0400 (AST) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 0013FD1B4E4 for ; Wed, 29 Oct 2003 20:57:28 -0400 (AST) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3842102; Wed, 29 Oct 2003 16:58:12 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Rob Nagler , pgsql-performance@postgresql.org Subject: Re: vacuum locking Date: Wed, 29 Oct 2003 16:55:07 -0800 User-Agent: KMail/1.4.3 References: <16272.318.870000.93584@gargle.gargle.HOWL> <87d6ciy3bf.fsf@stark.dyndns.tv> <16288.19970.172547.319577@jump.bivio.com> In-Reply-To: <16288.19970.172547.319577@jump.bivio.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200310291655.07363.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/739 X-Sequence-Number: 4487 Rob, > q5 and q6 are too complex to discuss here, but the fundamental issue > is the order in which postgres decides to do things. The choice for > me is clear: the developer time trying to figure out how to make the > planner do the "obviously right thing" has been too high with > postgres. These tests demonstate to me that for even complex queries, > oracle wins for our problem. >=20 > It looks like we'll be migrating to oracle for this project from these > preliminary results. It's not just the planner problems. The > customer is more familiar with oracle, and the vacuum performance is > another problem. Hey, we can't win 'em all. If we could, Larry would be circulating his=20 resume'. I hope that you'll stay current with PostgreSQL developments so that you ca= n=20 do a similarly thourough evaluation for your next project. --=20 -Josh Berkus Aglio Database Solutions San Francisco