Re: Experiences with extensibility

From: Sim Zacks <sim(at)compulab(dot)co(dot)il>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Experiences with extensibility
Date: 2008-01-09 07:26:56
Message-ID: fm1t4i$2pbg$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

You wrote that either it is not implemented well (catastrophic data losss) or is
expensive (Oracle) or it is a monopoly (MSSQL). None of those are easy.
Expensive and monopoly don't seem to me to be non-easy, rather undesirable if
you don't need to get into it.

When someone asks a question about a feature found in a commercial product and
the answer is that the feature is not available unless you accept on yourself
horrid possibilities, that is similar to Microsoft saying that sure you can use
open source, but there is no support, it is unreliable, ... Pure FUD. You can
call it reverse FUD, but it is FUD nonetheless.

We use postgresql because it is open source, we have in-house experience to deal
with it so we don't have any extra support costs and we don't need the features
that are offered in commercial products that PostGreSQL does not have. We also
don't need the speed that commercial products offer that is missing in PostgreSQL.

Sim

Joshua D. Drake wrote:
> Sim Zacks wrote:
>>
>> > That isn't really an extensibility argument. At least not in my mind.
>> > Further I don't know of anyone that can "easily" do it. You either
>> > suffer the possibility of catastrophic data loss (dolphins) or you
>> > suffer guaranteed bank account drainage (Oracle), or you suffer the
>> > willingness of Monopolies (MSSQL).
>> >
>> > None of those equate to "easy".
>>
>> That's a load of FUD. When looking at feature-sets that are available
>> or not
>> available in an open source product, you can't throw out all the
>> things that a
>> commercial, closed source project has because it isn't open source and
>> it costs
>> money.
>
> You obviously didn't read my post.
>
>>
>> The reason companies go with the closed source, expensive solutions is
>> because
>> they are better products.
>
> Sometimes, sometimes not. It depends on your needs.
>
>>
>> When evaluating a database for your company, it is better to look at
>> what the
>> closed source products offer that cause companies to shell out tons of
>> money and
>> decide if it is worth locking yourself into an expensive and/or
>> exclusive agreement.
>
> The only thing this post could possibly be is a Troll. Please go back
> under the bridge.
>
> Sincerely,
>
> Joshua D. rake
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ow Mun Heng 2008-01-09 07:27:54 Re: Experiences with extensibility
Previous Message Guido Neitzer 2008-01-09 07:24:36 Re: Experiences with extensibility