Re: How large can a PostgreSQL database get?

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "Aleksey Tsalolikhin *EXTERN*" <atsaloli(dot)tech(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: How large can a PostgreSQL database get?
Date: 2013-04-17 18:53:13
Message-ID: CAOzAquJHUV6ATm8+60FXJhBRd4Yj4-cLk3mWEQV-87=N_xWPxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 4/17/13, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> My experience, doing production and dev dba work on both postgresql
> and oracle, is that either works well, as long as you partition
> properly or even break things into silos. Oracle isn't magic pixie
> dust that suddenly gets hardware with 250MB/s seq read arrays to read
> at 1GB/s, etc.
>
> With oracle partitioning is easier, and everything else on the
> freaking planet is harder.

Scott, thank you for the best laugh I've had all day!

I started out on Oracle (some 20 years ago) and have been running both
MySQL and PostgreSQL databases for the last 10 years or so. I'd take
PostgreSQL over the other two in a heartbeat!

Data integrity/data preservation issues (backup is just one aspect of
that) are going to be your biggest problems with VERY large databases,
no matter how much money you throw at it.
--
Mike Nolan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dale Fukami 2013-04-17 19:07:26 Re: Mysterious table that exists but doesn't exist
Previous Message Alfonso Afonso 2013-04-17 18:48:42 Re: SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object