Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 3B1582E357D for ; Fri, 30 Nov 2007 11:45:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 31834-08 for ; Fri, 30 Nov 2007 11:45:57 -0400 (AST) Received: from chip2og50.obsmtp.com (chip2og50.obsmtp.com [64.18.13.37]) by postgresql.org (Postfix) with SMTP id 6C6362E3054 for ; Fri, 30 Nov 2007 11:45:57 -0400 (AST) Received: from source ([63.240.6.3]) (using TLSv1) by chip2ob50.postini.com ([64.18.5.12]) with SMTP; Fri, 30 Nov 2007 07:45:50 PST Received: from d01smtp07.Mi8.com ([172.16.1.114]) by Outbound02.Mi8.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 10:47:16 -0500 Received: from MI8NYCMAIL08.Mi8.com ([172.16.1.164]) by d01smtp07.Mi8.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Nov 2007 10:47:16 -0500 Received: from 69.181.101.67 ([69.181.101.67]) by MI8NYCMAIL08.Mi8.com ([172.16.1.190]) via Exchange Front-End Server mi8owa.mi8.com ([172.16.1.106]) with Microsoft Exchange Server HTTP-DAV ; Fri, 30 Nov 2007 15:46:53 +0000 User-Agent: Microsoft-Entourage/11.3.6.070618 Date: Fri, 30 Nov 2007 07:45:27 -0800 Subject: Re: TB-sized databases From: Luke Lonergan To: Pablo Alcaraz , pgsql-performance Message-ID: Thread-Topic: [PERFORM] TB-sized databases Thread-Index: AcgzaAcsRW/PXJ9bEdy5FgAbY6InMA== In-Reply-To: <474B1407.3090607@laotraesquina.com.ar> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 30 Nov 2007 15:47:16.0066 (UTC) FILETIME=[482E2C20:01C83368] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/400 X-Sequence-Number: 27815 Hi Peter, If you run into a scaling issue with PG (you will at those scales 1TB+), you can deploy Greenplum DB which is PG 8.2.5 compatible. A large internet company (look for press soon) is in production with a 150TB database on a system capable of doing 400TB and we have others in production at 60TB, 40TB, etc. We can provide references when needed - note that we had 20 successful customer references supporting Gartner's magic quadrant report on data warehouses which put Greenplum in the "upper visionary" area of the magic quadrant - which only happens if your customers can scale (see this: http://www.esj.com/business_intelligence/article.aspx?EditorialsID=8712) In other words, no matter what happens you'll be able to scale up with your Postgres strategy. - Luke On 11/26/07 10:44 AM, "Pablo Alcaraz" wrote: > I had a client that tried to use Ms Sql Server to run a 500Gb+ database. > The database simply colapsed. They switched to Teradata and it is > running good. This database has now 1.5Tb+. > > Currently I have clients using postgresql huge databases and they are > happy. In one client's database the biggest table has 237Gb+ (only 1 > table!) and postgresql run the database without problem using > partitioning, triggers and rules (using postgresql 8.2.5). > > Pablo > > Peter Koczan wrote: >> Hi all, >> >> I have a user who is looking to store 500+ GB of data in a database >> (and when all the indexes and metadata are factored in, it's going to >> be more like 3-4 TB). He is wondering how well PostgreSQL scales with >> TB-sized databases and what can be done to help optimize them (mostly >> hardware and config parameters, maybe a little advocacy). I can't >> speak on that since I don't have any DBs approaching that size. >> >> The other part of this puzzle is that he's torn between MS SQL Server >> (running on Windows and unsupported by us) and PostgreSQL (running on >> Linux...which we would fully support). If any of you have ideas of how >> well PostgreSQL compares to SQL Server, especially in TB-sized >> databases, that would be much appreciated. >> >> We're running PG 8.2.5, by the way. >> >> Peter >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 4: Have you searched our list archives? >> >> http://archives.postgresql.org >> >> > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings