Re: PGSQL Locking vs. Oracle's MVCC - Mailing list pgsql-general

From Merlin Moncure
Subject Re: PGSQL Locking vs. Oracle's MVCC
Date
Msg-id b42b73150702230538h3c287bdblec73179a1d2944c7@mail.gmail.com
Whole thread Raw
In response to Re: PGSQL Locking vs. Oracle's MVCC  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-general
On 2/23/07, Tomas Vondra <tv@fuzzy.cz> wrote:
> Sure, there are many differences when it comes to internals (Albe
> Laurenz already pointed out the
> most obvious one), as well as the Oracle is superior in many areas
> (partitioning, some features in
> PL/SQL, etc.).
>
> This generally means that if you have an application architecture for
> PostgreSQL, then it will usually
> work fine Oracle. If the constraint is correctly enforced in PostgreSQL,
> then it will be enforced in
> Oracle etc.


be careful with that statement....some of the internals are better and
some are worse.  all postgresql ddl is transactional for example.  how
easily the code ports is going to depend on how tweaky the developers
were...it's very easy to fall in love with postgresql-specific
features and write unportable code.

merlin

pgsql-general by date:

Previous
From: Dave Page
Date:
Subject: Ruby on Rails for PostgreSQL
Next
From: "Anton Melser"
Date:
Subject: select all matches for a regular expression ?