Swaminathan Saikumar wrote:
> Hi all,
> I'm new to PostGreSql.
What a wonderful article - it's almost worth keeping a copy. It's so bad
it's difficult to know where to start. I think my favourite has to be :
+ MSSql being massive is considered to have the maximum scalability for
And I just love the comment on both MySQL and Postgres about GPL and BSD
being 'too open' - meaning?
> Check out the link. I am starting out on a new personal project & had
> zeroed in on PostGreSql with Mono-ASP.NET as ideal for my needs,
> mainly owing to a PostGreSql whitepaper.
> Now, I chanced upon the article above. I've pasted the cons as
> mentioned in the article, and would like the community feedback on it,
> especially with regards to the "inferior Data Storage mechanism".
> The cons of PostgreSql Hosting
> * Performance considerations: Inserts and Updates into the PostgreSql
> database is much slower compared to MySql. PostgreSql hosting thus
> might slow down the display of the web page online.
> * BSD license issues: Since PostgreSql comes under the Berkeley
> license scheme, this is again considered to be too open.
> * Availability of inferior Data Storage mechanism: PostgreSql uses
> Postgres storage system, which is not considered to be transaction sae
> during PostgreSql hosting.
> * Its not far-flung: While MySql hosting and MSSql hosting have deeply
> penetrated into the market, PostgreSql hosting still remains to be
> passive in the database hosting market.
> * Non-availability of required assistance for PostgreSql hosting:
> Assistance is being provided via mailing lists. However there is no
> guarantee that the issue faced during PostgreSql hosting would be
In response to
pgsql-general by date
|Next:||From: Scott Marlowe||Date: 2008-01-31 00:56:53|
|Subject: Re: Is PostGreSql's Data storage mechanism "inferior"?|
|Previous:||From: Guillaume Lelarge||Date: 2008-01-31 00:52:34|
|Subject: Re: monitoring fragmentation|