X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4189CD1B1AA for ; Tue, 29 Jun 2004 15:15:52 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31014-06 for ; Tue, 29 Jun 2004 18:15:44 +0000 (GMT) Received: from pc7.berlin.powerweb.de (pc7.berlin.powerweb.de [62.67.228.13]) by svr1.postgresql.org (Postfix) with ESMTP id 0D723D1B17B for ; Tue, 29 Jun 2004 15:15:42 -0300 (ADT) Received: from spock (p508409B6.dip0.t-ipconnect.de [80.132.9.182]) by pc7.berlin.powerweb.de (8.9.3p3/8.9.3) with SMTP id UAA04409; Tue, 29 Jun 2004 20:15:38 +0200 Message-ID: <004e01c45e05$3401b0f0$6602a8c0@spock> From: "Harald Lau (Sector-X)" To: "Scott Marlowe" Cc: References: <007d01c45da4$3726dcd0$6602a8c0@spock> <40E11BF0.3020109@familyhealth.com.au> <00b801c45db5$914330e0$6602a8c0@spock> <1088529718.12350.35.camel@localhost.localdomain> Subject: Re: no index-usage on aggregate-functions? Date: Tue, 29 Jun 2004 20:16:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_NJABL, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200406/310 X-Sequence-Number: 7368 > Note that there ARE other options. While the inability to provide a > speedy count is a "cost" of using an MVCC system, the ability to allow > thousands of readers to run while updates are happening underneath them > more than makes up for the slower aggregate performance. IMO this depends on the priority of your application resp. the customers in= tentions and wishes > This, however, is not paradise. you can't have it all ;-) > On the contrary, it makes it GREAT for datawarehousing. Not because any > one child process will be super fast, but because ALL the child > processes will run reasonably fast, even under very heavy read and write > load. What I meant with datawarehouse are many db's at many locations whose data = are to be collected in one central db in order to mix em up, sum up or do a= nything equivalent. But in fact my quite heavy-read/write-accessed db is running really fast si= nce 1 1/2 years now Even though still on PG 7.2 The one and only bottleneck are the statistics and the reports - and the ta= bles are getting larger and larger ... > Note that if you've got the memory for the hash agg algo to fire > into shared memory, it's pretty darned fast now, yes, I've noticed here on the testing server > so if the data (mostly) > fit into kernel cache you're gold. And 12 gig Intel boxes aren't that > expensive, compared to an Oracle license. *that's* the point ... Anyway: Greetings and thanks for your answers Harald