Andrew Rawnsley wrote:
> On Apr 9, 2004, at 4:58 AM, Tim Pizey wrote:
>> What can Oracle do that PG can't ?
> Bankrupt you? Make your hair fall out? Cause ulcers? The list is
pro: OLAP, recursive queries, clustering, tablespaces, advanced queuing,
bitmap indexing, index organized tables, materialized views, database
links, nested tables, cubes, ... (just to name a few).
contra: bankrupt you, driver your dbas crazy, malloc(size_of(ram) * 1000)
Don't get me wrong. PostgreSQL is a damn good product and it supports
95% of all commonly used features.
However, it is not time yet to tell that we can do EVERYTHING oracle can
do and that Oracle is already completely obsolete. There are still areas
which cannot be covered with PostgreSQL
For a "normal" database PostgreSQL is definitely the better choice but
when working with cubes and so forth it can be damn hard. More work is
needed to make PostgreSQL support these features.
Cybertec Geschwinde u Schoenig
Schoengrabern 134, A-2020 Hollabrunn, Austria
Tel: +43/2952/30706 or +43/664/233 90 75
www.cybertec.at, www.postgresql.at, kernel.cybertec.at
In response to
pgsql-jdbc by date
|Next:||From: Oliver Jowett||Date: 2004-04-09 13:53:59|
|Subject: patch: fix ResultSet.isLast and friends with cursor-based resultsets|
|Previous:||From: Andrew Rawnsley||Date: 2004-04-09 11:13:01|
|Subject: Re: [OT] Porting from Oracle [was Connection Idle in transaction]|