Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-advocacy] [PERFORM] Postgres VS Oracle

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [pgsql-advocacy] [PERFORM] Postgres VS Oracle
Date: 2007-06-19 13:39:02
Message-ID: 60ps3sdpxl.fsf@dba2.int.libertyrms.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-advocacypgsql-generalpgsql-novicepgsql-performance
walterc(at)indiana(dot)edu (Carol Walter) writes:
> I don't want to add gas to the flamewar, but I gotta ask.  What is in
> the the 90 to 95% referred to in this email.

I'd say, look at the Oracle feature set for things that it has that
PostgreSQL doesn't.

Four that come to mind:

- ORAC = multimaster replication
- Integration with hardware vendors' High Availability systems
- Full fledged table partitioning
- Windowing functions (SQL:2003 stuff, used in OLAP)

These are features Truly Needed for a relatively small percentage of
systems.  They're typically NOT needed for:

 - departmental applications that operate during office hours
 - light weight web apps that aren't challenging the limits of
   the most expensive hardware
 - any application where reliability requirements do not warrant
   spending $1M to make it more reliable
 - applications that make relatively unsophisticated use of data
   (e.g. - it's not worth the analysis to figure out a partitioning
   design, and nobody's running queries so sophisticated that they
   need windowing analytics)

I expect both of those lists are incomplete, but those are big enough
lists to, I think, justify the claim, at least in loose terms.

The most important point is that third one, I think: 
  "any application where reliability requirements do not warrant
  spending $1M to make it more reliable"

Adopting ORAC and/or other HA technologies makes it necessary to spend
a Big Pile Of Money, on hardware and the humans to administer it.

Any system whose importance is not sufficient to warrant *actually
spending* an extra $1M on improving its reliability is *certain* NOT
to benefit from either ORAC or HA, because you can't get any relevant
benefits without spending pretty big money.  Maybe the number is lower
than $1M, but I think that's the right order of magnitude.
-- 
output = reverse("ofni.secnanifxunil" "@" "enworbbc")
http://linuxdatabases.info/info/nonrdbms.html
"One disk to rule them all,  One disk to find  them. One disk to bring
them all and in the darkness grind them. In  the Land of Redmond where
the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh

In response to

Responses

pgsql-novice by date

Next:From: Chris BrowneDate: 2007-06-19 13:49:45
Subject: Re: [pgsql-advocacy] [PERFORM] Postgres VS Oracle
Previous:From: LewDate: 2007-06-19 13:38:30
Subject: Re: Postgres VS Oracle

pgsql-performance by date

Next:From: Gregory StarkDate: 2007-06-19 13:46:18
Subject: Re: Performance query about large tables, lots of concurrent access
Previous:From: LewDate: 2007-06-19 13:38:30
Subject: Re: Postgres VS Oracle

pgsql-admin by date

Next:From: Chris BrowneDate: 2007-06-19 13:49:45
Subject: Re: [pgsql-advocacy] [PERFORM] Postgres VS Oracle
Previous:From: LewDate: 2007-06-19 13:38:30
Subject: Re: Postgres VS Oracle

pgsql-advocacy by date

Next:From: Chris BrowneDate: 2007-06-19 13:49:45
Subject: Re: [pgsql-advocacy] [PERFORM] Postgres VS Oracle
Previous:From: LewDate: 2007-06-19 13:38:30
Subject: Re: Postgres VS Oracle

pgsql-general by date

Next:From: Alvaro HerreraDate: 2007-06-19 13:40:02
Subject: Re: pg_restore out of memory
Previous:From: LewDate: 2007-06-19 13:38:30
Subject: Re: Postgres VS Oracle

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group