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 C2853D1B55F for ; Thu, 30 Oct 2003 00:03:48 +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 29587-01 for ; Wed, 29 Oct 2003 20:03:19 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id B12EDD1B544 for ; Wed, 29 Oct 2003 20:03:16 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h9U03Iit024019; Wed, 29 Oct 2003 19:03:18 -0500 (EST) To: Rob Nagler Cc: pgsql-performance@postgresql.org Subject: Re: vacuum locking In-reply-to: <16288.19970.172547.319577@jump.bivio.com> References: <16272.318.870000.93584@gargle.gargle.HOWL> <16279.4988.496000.539525@gargle.gargle.HOWL> <200310230814.56738.mweilguni@sime.com> <29123.1066915615@sss.pgh.pa.us> <16279.61590.158000.290397@gargle.gargle.HOWL> <87vfqeveab.fsf@stark.dyndns.tv> <16281.45354.209000.280418@gargle.gargle.HOWL> <878ynaupgu.fsf@stark.dyndns.tv> <16285.17811.994000.543635@gargle.gargle.HOWL> <87d6ciy3bf.fsf@stark.dyndns.tv> <16288.19970.172547.319577@jump.bivio.com> Comments: In-reply-to Rob Nagler message dated "Wed, 29 Oct 2003 16:32:18 -0700" Date: Wed, 29 Oct 2003 19:03:18 -0500 Message-ID: <24018.1067472198@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/737 X-Sequence-Number: 4485 Rob Nagler writes: > q5 and q6 are too complex to discuss here, How do you expect us to get better if you don't show us the problems? BTW, have you tried any of this with a 7.4beta release? Another project that I'm aware of saw several bottlenecks in their Oracle-centric code go away when they tested 7.4 instead of 7.3. For instance, there is hash aggregation capability, which would probably solve the aggregate query problem you were complaining about in http://archives.postgresql.org/pgsql-performance/2003-10/msg00640.php regards, tom lane