Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 8FFC71337B8D for ; Fri, 4 Feb 2011 04:50:55 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 85893-04 for ; Fri, 4 Feb 2011 08:50:49 +0000 (UTC) Received: from news.hub.org (news.hub.org [200.46.204.72]) by mail.postgresql.org (Postfix) with ESMTP id B88241337B82 for ; Fri, 4 Feb 2011 04:50:47 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.4/8.14.4) with ESMTP id p148ok4w013539 for ; Fri, 4 Feb 2011 04:50:46 -0400 (AST) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.4/8.14.4/Submit) id p148hOVZ099034 for pgsql-performance@postgresql.org; Fri, 4 Feb 2011 04:43:24 -0400 (AST) (envelope-from news) From: =?ISO-8859-1?Q?Torsten_Z=FChlsdorff?= X-Newsgroups: pgsql.performance Subject: Re: [HACKERS] Slow count(*) again... Date: Fri, 04 Feb 2011 09:43:23 +0100 Organization: A noiseless patient Spider Lines: 27 Message-ID: References: <201102012247.p11Ml6u02682@momjian.us> <4D48914B.4050403@dunslane.net> <4D489AD1.1010105@vmsinfo.com> <4D499E55.4020107@vmsinfo.com> <4D49A6B9.4060608@2ndquadrant.com> <4D49C482.4010707@vmsinfo.com> <4D49F0BA.9000901@2ndquadrant.com> <4D4A16BF.1020304@vmsinfo.com> <4D4A4844.3020409@2ndquadrant.com> <4D4AD9F6.6040903@vmsinfo.com> <4D4AE16E.9040807@peak6.com> <4D4B17B4.9030406@vmsinfo.com> <4D4B1F5B.4060403@peak6.com> <4D4B261B.6010303@vmsinfo.com> <4D4B2E8A.7010402@vmsinfo.com> <4D4ADF42020000250003A34C@gw.wicourts.gov> <4D4B3B41.7060803@vmsinfo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 4 Feb 2011 08:43:24 +0000 (UTC) Injection-Info: mx03.eternal-september.org; posting-host="AnkPUomeHXvuN7UdHvIkog"; logging-data="13237"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1++jHVCwUGp+lVKL5TIXyl4" User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0 In-Reply-To: <4D4B3B41.7060803@vmsinfo.com> Cancel-Lock: sha1:4MTDjbIHaohwepbgV5Vpu5LKYMM= To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201102/175 X-Sequence-Number: 42313 Mladen Gogala schrieb: > Well, the problem will not go away. As I've said before, all other > databases have that feature and none of the reasons listed here > convinced me that everybody else has a crappy optimizer. The problem > may go away altogether if people stop using PostgreSQL. A common problem of programmers is, that they want a solution they already know for a problem they already know, even if it is the worst solution the can choose. There are so many possibilities to solve a given problem and you even have time to do this before your application get released. Also: if you rely so heavily on hints, then use a database which supports hints. A basic mantra in every training i have given is: use the tool/technic/persons which fits best for the needs of the project. There are many databases out there - choose for every project the one, which fits best! Greetings from Germany, Torsten -- http://www.dddbl.de - ein Datenbank-Layer, der die Arbeit mit 8 verschiedenen Datenbanksystemen abstrahiert, Queries von Applikationen trennt und automatisch die Query-Ergebnisse auswerten kann.