| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Tomas Vondra" <tv(at)fuzzy(dot)cz> |
| Cc: | RPK <rohitprakash123(at)indiatimes(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PGSQL Locking vs. Oracle's MVCC |
| Date: | 2007-02-23 13:38:39 |
| Message-ID: | b42b73150702230538h3c287bdblec73179a1d2944c7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/23/07, Tomas Vondra <tv(at)fuzzy(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anton Melser | 2007-02-23 14:00:53 | select all matches for a regular expression ? |
| Previous Message | Dave Page | 2007-02-23 13:25:25 | Ruby on Rails for PostgreSQL |