Alex Avriette <a_avriette@acs.org> writes:
> Dont beat yourself up, guys, over making postgres a drop-in replacement for
> Oracle. The people that would benefit from actually "dropping in" postgres
> into an Oracle install will have already eased the burden on themselves by
> being responsible in their database construction and programming. I haven't
> even been able to convince our Oracle guys that Postgres is actually a "real
> database" (its free?!! how can it be free?!). They would never, (ever!)
> consider dropping in postgres. If you're intent on taking "customers" from
> Oracle, catch them where youll be able to convert them -- before Oracle is
> even installed.
In principle, I agree with you. However, my company (Zembu) has a
business need for better Oracle compatibility, based on real customer
need.
Zembu doesn't don't have a need to make Postgres a drop-in replacement
for Oracle; that is a nearly impossible task in any case, because
Oracle DBAs don't know how to manage Postgres, and most don't want to
learn. Zembu does have a need to permit applications to speak to both
Oracle and Postgres.
Just to be clear, I am not on the Postgres development team. I'm
talking about work which is important for Zembu, and which I believe
can be quite helpful to Postgres in general. I'm trying to structure
the work so that even if accepted it would not take too many cycles
away from core Postgres development.
Ian
