pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Jayadevan M <Jayadevan.Maymala@ibsplc.com>
Cc: pgsql-general@postgresql.org, pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: [PERFORM] PostgreSQL - case studies
Date: Wed, 10 Feb 2010 10:55:03 -0500
Message-ID: <20100210155503.GB17756@tamriel.snowman.net> (raw)
In-Reply-To: <4B7280C7020000250002F120@gw.wicourts.gov>
References: <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com>
	<4B7280C7020000250002F120@gw.wicourts.gov>

* 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)?

Just saw this, so figured I'd comment:

tsf=> \l+
                                                              List of databases
   Name    |  Owner   | Encoding |  Collation  |    Ctype    |     Access privileges      |  Size   | Tablespace  |        Description        
-----------+----------+----------+-------------+-------------+----------------------------+---------+-------------+---------------------------
 beac      | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =Tc/postgres               | 1724 GB | pg_default  | 

Doesn't look very pretty, but the point is that its 1.7TB.  There's a
few other smaller databases on that system too.  PG handles it quite
well, though this is primairly for data-mining.

	Thanks,

		Stephen

Attachments:

  signature.asc (application/pgp-signature, 196B) download

view thread (7+ messages)  latest in thread

Message-ID: <20100210155503.GB17756@tamriel.snowman.net>
Permalink:  ../20100210155503.GB17756@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20100210155503.GB17756@tamriel.snowman.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: sfrost@snowman.net, Kevin.Grittner@wicourts.gov, Jayadevan.Maymala@ibsplc.com
  Subject: Re: [PERFORM] PostgreSQL - case studies
  In-Reply-To: <20100210155503.GB17756@tamriel.snowman.net>
  References: <OFE0550409.E8DBE5B8-ON652576C6.0014526C-652576C6.001716AC@ibsplc.com> <4B7280C7020000250002F120@gw.wicourts.gov> <20100210155503.GB17756@tamriel.snowman.net>

* 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