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 6F1733A490F for ; Thu, 20 Jan 2005 20:00:36 +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 68579-04 for ; Thu, 20 Jan 2005 20:00:22 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id 300383A48DF for ; Thu, 20 Jan 2005 20:00:22 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1CriTZ-0008EL-00; Thu, 20 Jan 2005 15:00:17 -0500 To: =?iso-8859-1?q?Herv=E9_Piedvache?= Cc: "Bruno Almeida do Lago" , pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering References: <005701c4ff1b$42c0ada0$e883f40a@br.gedasgrp> <200501202000.03853.herve@elma.fr> In-Reply-To: <200501202000.03853.herve@elma.fr> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 20 Jan 2005 15:00:17 -0500 Message-ID: <87651rdg6m.fsf@stark.xeocode.com> Lines: 30 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 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.056 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/339 X-Sequence-Number: 10029 Hervé Piedvache writes: > Le Jeudi 20 Janvier 2005 19:09, Bruno Almeida do Lago a écrit : > > Could you explain us what do you have in mind for that solution? I mean, > > forget the PostgreSQL (or any other database) restrictions and explain us > > how this hardware would be. Where the data would be stored? > > > > I've something in mind for you, but first I need to understand your needs! > > I just want to make a big database as explained in my first mail ... At the > beginning we will have aprox. 150 000 000 records ... each month we will add > about 4/8 millions new rows in constant flow during the day ... and in same > time web users will access to the database in order to read those data. > Stored data are quite close to data stored by google ... (we are not making a > google clone ... just a lot of data many small values and some big ones ... > that's why I'm comparing with google for data storage). > Then we will have a search engine searching into those data ... You're concentrating on the data within the database. That's only half the picture. What are you going to *do* with the data in the database? You need to analyze what "we will have a search engine searching into those data" means in more detail. Postgres is more than capable of storing 150Gb of data. There are people with terabyte databases on this list. You need to define what types of queries you need to perform, how many data they need to manipulate, and what your performance requirements are for those queries. -- greg