pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Victor Nawothnig <victor.nawothnig@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL vs Oracle
Date: Sun, 21 Dec 2008 01:51:19 -0700
Message-ID: <dcc563d10812210051k57d0c304rcdd7c668b572ce9e@mail.gmail.com> (raw)
In-Reply-To: <9ad9b6b70812210017q7b90aec6g4540ed1e74ca1ca1@mail.gmail.com>
References: <9ad9b6b70812210017q7b90aec6g4540ed1e74ca1ca1@mail.gmail.com>

On Sun, Dec 21, 2008 at 1:17 AM, Victor Nawothnig
<victor.nawothnig@gmail.com> wrote:
> Hi,
>
> I am looking for some recent and hopefully genuine comparisons between
> Oracle and PostgreSQL regarding their performance in large scale
> applications. Tests from real world applications would be preferable
> but not required. Also differentiations in different areas (i.e.
> different data types, query structures, clusters, hardware, etc.)
> might be helpful as well.

Due to the terms of the license for Oracle, no one can publish
benchmarks without their permission.

Having used both Oracle 9 and pgsql from 6.5 to 8.3, I can say that
PostgreSQL is competitive for most small to medium loads I've thrown
at it, and given the high cost of licensing for oracle, you can throw
a LOT of hardware at PostgreSQL to catch up the last 10 or 20%
slowdown you might see in some apps.

Most of Oracle's advantages are in the more advanced features like
partitioning and reporting functions.

That said, I find PostgreSQL takes a LOT less administration to keep
it happy.  Oracle doesn't just allow a wider range of performance
tuning, it demands it.  If you don't demonstrably need Oracle's
advanced features then PostgreSQL is usually a better choice.

Last place we worked we developed on pgsql and migrated to oracle in
production (this was in the 7.4 era, when Oracle 9 was noticeably
faster and better than pgsql for transactional loads.)  It was very
easy to write for pgsql and migrate to oracle as most SQL queries
didn't need any serious changes from one db to the other.

PostgreSQL generally tries to follow the SQL specs a little closer,
oracle has more crufty legacy stuff in it.

So, when you say large scale applications, are you talking OLTP or
OLAP type workloads?  My experience has been that very few OLTP apps
get very large, as they get partitioned before they get over a few
dozen gigabytes.  OLAP, OTOH, often run into hundreds of Gigs or
terabytes.   I've found pgsql competitive in both really.



view thread (4+ messages)  latest in thread

Message-ID: <dcc563d10812210051k57d0c304rcdd7c668b572ce9e@mail.gmail.com>
Permalink:  ../dcc563d10812210051k57d0c304rcdd7c668b572ce9e@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10812210051k57d0c304rcdd7c668b572ce9e@mail.gmail.com

 · 

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: scott.marlowe@gmail.com, victor.nawothnig@gmail.com
  Subject: Re: PostgreSQL vs Oracle
  In-Reply-To: <dcc563d10812210051k57d0c304rcdd7c668b572ce9e@mail.gmail.com>
  References: <9ad9b6b70812210017q7b90aec6g4540ed1e74ca1ca1@mail.gmail.com> <dcc563d10812210051k57d0c304rcdd7c668b572ce9e@mail.gmail.com>

* 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