pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Mair <chris@1006.org>
To: Brian Hurt <bhurt@janestcapital.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: Postgres and really huge tables
Date: Thu, 18 Jan 2007 22:42:40 +0100
Message-ID: <45AFE9D0.6060205@1006.org> (raw)
In-Reply-To: <45AFD927.9050605@janestcapital.com>
References: <4939.1164740825@sss.pgh.pa.us>
	<200611282344.kASNijt09203@momjian.us>
	<456CE066.50803@cheapcomplexdevices.com>
	<456D8A65.3080400@janestcapital.com>
	<1164812624.9690.500.camel@archimedes>
	<456DA476.4000606@janestcapital.com>
	<456DB8C9.7020206@cheapcomplexdevices.com>
	<45AFD927.9050605@janestcapital.com>


> Is there any experience with Postgresql and really huge tables?  I'm 
> talking about terabytes (plural) here in a single table.  Obviously the 
> table will be partitioned, and probably spread among several different 
> file systems.  Any other tricks I should know about?
> 
> We have a problem of that form here.  When I asked why postgres wasn't 
> being used, the opinion that postgres would "just <explicitive> die" was 
> given.  Personally, I'd bet money postgres could handle the problem (and 
> better than the ad-hoc solution we're currently using).  But I'd like a 
> couple of replies of the form "yeah, we do that here- no problem" to 
> wave around.

I've done a project using 8.1 on solaris that had a table that was 
closed to 2TB. The funny thing is that it just worked fine even without 
partitioning.

But, then again: the size of a single record was huge too: ~ 50K.
So there were not insanly many records: "just" something
in the order of 10ths of millions.

The queries just were done on some int fields, so the index of the
whole thing fit into RAM.

A lot of data, but not a lot of records... I don't know if that's
valid. I guess the people at Greenplum and/or Sun have more exciting
stories ;)


Bye, Chris.






view thread (10+ messages)  latest in thread

Message-ID: <45AFE9D0.6060205@1006.org>
Permalink:  ../45AFE9D0.6060205@1006.org/
Also on:    postgresql.org/message-id/45AFE9D0.6060205@1006.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: chris@1006.org, bhurt@janestcapital.com, pgsql-advocacy@postgresql.org
  Subject: Re: Postgres and really huge tables
  In-Reply-To: <45AFE9D0.6060205@1006.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox