Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id AD477633222;
	Wed, 10 Feb 2010 12:16:41 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024)
	with ESMTP id 52632-05; Wed, 10 Feb 2010 16:16:31 +0000 (UTC)
X-Greylist: delayed 00:05:55.57333 by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from skunk.mtbrook.bozemanpass.com (skunk.mtbrook.bozemanpass.com
	[69.145.82.195])
	by mail.postgresql.org (Postfix) with ESMTP id 343C1633218;
	Wed, 10 Feb 2010 12:16:31 -0400 (AST)
Received: from [69.145.82.252] (unknown [69.145.82.252])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by skunk.mtbrook.bozemanpass.com (Postfix) with ESMTP id A831655803E;
	Wed, 10 Feb 2010 09:17:10 -0800 (PST)
Message-ID: <4B72DA77.2050802@boreham.org>
Date: Wed, 10 Feb 2010 09:10:31 -0700
From: David Boreham <david_list@boreham.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
CC: pgsql-general@postgresql.org,
	pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: [PERFORM] PostgreSQL - case studies
References: 
 <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com>
	<4B7280C7020000250002F120@gw.wicourts.gov>
	<20100210155503.GB17756@tamriel.snowman.net>
In-Reply-To: <20100210155503.GB17756@tamriel.snowman.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.185 tagged_above=-10 required=5
	tests=BAYES_40=-0.185
X-Spam-Level: 
X-Archive-Number: 201002/448
X-Sequence-Number: 159224

Kevin Grittner (Kevin.Grittner@wicourts.gov) wrote:
>>> Could some of you please share some info on such scenarios- where
>>> you are supporting/designing/developing databases that run into at
>>> least a few hundred GBs of data (I know, that is small by todays'
>>> standards)?
>>>       
At NuevaSync we use PG in a one-database-per-server design, with our own
replication system between cluster nodes. The largest node has more than 
200G online.
This is an OLTP type workload.