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 1CBEC56526 for ; Tue, 1 Mar 2005 14:01:51 +0000 (GMT) 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 56727-05 for ; Tue, 1 Mar 2005 14:01:49 +0000 (GMT) Received: from mail.logi-track.com (www.logi-track.com [213.239.193.212]) by svr1.postgresql.org (Postfix) with ESMTP id A48845651B for ; Tue, 1 Mar 2005 14:01:49 +0000 (GMT) Received: from kingfisher.intern.logi-track.com (pD95DCE38.dip0.t-ipconnect.de [217.93.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logi-track.com (Postfix) with ESMTP id 746FC307FB; Tue, 1 Mar 2005 15:01:56 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logi-track.com (Postfix) with ESMTP id E500EAB388; Tue, 1 Mar 2005 15:01:50 +0100 (CET) Message-ID: <422475CE.9030507@logi-track.com> Date: Tue, 01 Mar 2005 15:01:50 +0100 From: Markus Schaber User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Ramon Bastiaans Cc: pgsql-performance@postgresql.org Subject: Re: multi billion row tables: possible or insane? References: <42243725.6060804@sara.nl> In-Reply-To: <42243725.6060804@sara.nl> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.115 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/6 X-Sequence-Number: 10711 Hi, Ramon, Ramon Bastiaans schrieb: > The database's performance is important. There would be no use in > storing the data if a query will take ages. Query's should be quite fast > if possible. Which kind of query do you want to run? Queries that involve only a few rows should stay quite fast when you set up the right indices. However, queries that involve sequential scans over your table (like average computation) will take years. Get faaaaaast I/O for this. Or, better, use a multidimensional data warehouse engine. Those can precalculate needed aggregate functions and reports. But they need loads of storage (because of very redundant data storage), and I don't know any open source or cheap software. Markus -- markus schaber | dipl. informatiker logi-track ag | rennweg 14-16 | ch 8001 zürich phone +41-43-888 62 52 | fax +41-43-888 62 53 mailto:schabios@logi-track.com | www.logi-track.com