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

Fw: Oracle2PostgreSQL Migration with PL/pgSQL

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Advocacy" <pgsql-advocacy(at)postgresql(dot)org>
Subject: Fw: Oracle2PostgreSQL Migration with PL/pgSQL
Date: 2003-03-10 07:31:10
Message-ID: 009201c2e6d7$059149c0$6500a8c0@fhp.internal (view raw, whole thread or download thread mbox)
Lists: pgsql-advocacy
Saw this in the Oracle newsgroup...


----- Original Message -----
From: "DA Morgan" <damorgan(at)exesolutions(dot)com>
Sent: Sunday, March 09, 2003 6:40 AM
Subject: Re: Oracle2PostgreSQL Migration with PL/pgSQL

> Guido Stepken wrote:
> > Hi, out there !
> >
> > I am writing on a Oracle to PostgreSQL migration handbook.
> >
> > Seems, that PostgreSQL 7.4 (still beta) works quite fine in emulating
> > pl/SQL language. Clustering, MVCC (Multi Versioning Concurrency
> > Control), hot backup ... large databases (> 1 Tera), Query
> > caching/hashing, server side scripting with pl/pgSQL emulation seems to
> > work now. Very powerful RAD tools exist for postgresql. Oracle tools can
> > be used for development, due to compatibility.
> >
> > PostgreSQL IMHO more and more becomes a Oracle killer. Worth, writing a
> > small book about it ;-)
> >
> > I am still seeking small documentation / experiences, perhaps pl/SQL ->
> > pl/pgSQL code for comparisons, benchmarks (yes, i know, difficult to
> > interpret), experiences with toolkits (RAD, UML ...)....code should be
> > unter a free license for being published, if possible.......
> >
> > any hints welcome
> >
> > tnx in advance, Guido Stepken (mailto:stepken @ little -
> I love this from the PostgreSQL web site:
> "Multi-version concurrency control(MVCC)
> This removes our old table-level locking, and replaces it with a locking
> system that is superior to most commercial database systems. In a
> traditional system, each row that is modified is locked until committed,
> preventing reads by other users. MVCC uses the natural multi-version
> of PostgreSQL to allow readers to continue reading consistent data during
> writer activity. Writers continue to use the compact pg_log transaction
> system. This is all performed without having to allocate a lock for every

> row like traditional database systems. So, basically, we no longer are
> restricted by simple table-level locking; we have something better than
> row-level locking."
> Apparently copying the design of the Oracle counts as doing something not
> done by "traditional" database systems. Nothing like marketing folks to
> in integrity. If Oracle isn't a "traditional" database system ... I'd like
> to know what is.
> The day PostgreSQL and Oracle killer? I'd check the label on the
> medication.  ;-)
> Not that it is a bad product. But anytime they get in Larry or Bill's way
> ... they'll do to them what was done to Fox and Informix.
> Daniel Morgan

pgsql-advocacy by date

Next:From: Devrim GUNDUZDate: 2003-03-10 18:51:36
Subject: Re: [ADMIN] uppercase = lowercase
Previous:From: Mundo de Ingles de DIsneyDate: 2003-03-09 01:27:24
Subject: Por la preparacion de sus hijos...

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