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.
On Wed, Apr 17, 2013 at 8:15 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
> Aleksey Tsalolikhin wrote:
>> Hi. I was promoting PostgreSQL to an AIX/Oracle shop yesterday, they are looking to switch to open
>> source to cut their licensing costs, and was asked how large a database does PostgreSQL support? Is
>> there an upper bound on database size and if so, what it is?
>
> There is no real upper bound.
>
> I think that backup will be a limiting factor, and you'll want backups.
> Of course, sequential scans of really large tables will be very
> painful, but that's the same for all database systems.
>
> Yours,
> Laurenz Albe
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
To understand recursion, one must first understand recursion.