Re: Problem with recent PostgreSQL relatedpressrelease

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Advocacy List <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Problem with recent PostgreSQL relatedpressrelease
Date: 2007-07-13 20:24:19
Message-ID: 4697DF73.4030206@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

Jonah H. Harris wrote:
> On 7/13/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> That kind of makes my point :)
> The fact is, if you write a PostgreSQL-only app, it will run perfectly
> on PostgreSQL or EnterpriseDB.

But that isn't what I asked. I asked if I wrote an EnterpriseDB app
would it run on PostgreSQL, the answer is clearly no. Yes, yes we can of
course not use Enterprise (Oracle) features, but one of the benefits of
EnterpriseDB is that I "can" use those Oracle features.

That is my only point.

Joshua D. Drake

> Like Dave and I said, it's
> EnterpriseDB's policy to ensure that PostgreSQL compatibility is fully
> maintained.
>

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2007-07-13 20:31:23 Re: Problem with recent PostgreSQL relatedpressrelease
Previous Message Jonah H. Harris 2007-07-13 20:23:28 Re: Problem with recent PostgreSQL relatedpressrelease