Re: [GENERAL] info on people running postgre

Personally, I find PostgreSQL to be good for non mission critical databases.
I have used it for many commercial sites, but none that are "heavy" usage,
zero down time. PostgreSQL is a fine database with many features, but there
are database recovery/space usage issues that, I think, keep it from being
usable for all applications. The SQL engine is for the most part ANSI
compliant and the SQL translates well to other databases like Oracle. I
don't know about user defined database level functions...those probably
require rewriting. Performance wise, postgreSQL is fast. If there are
probs then you probably have run into the few performance tweak issues that
you can find listed in the archives...

The fact that you are coughing at $2000 dollars probably indicates that the
application isn't mission critical and postgreSQL probably would work fine
as long as you keep in mind that backups are very important in postgreSQL
and that vacuuming often will save you lots of headaches.

-----Original Message-----
From: Eric Enockson <eric(at)broken(dot)net>
To: pgsql-general(at)postgreSQL(dot)org <pgsql-general(at)postgreSQL(dot)org>
Date: Thursday, March 25, 1999 1:59 AM
Subject: [GENERAL] info on people running postgre

> hi,
>
> I am going to be implementing an online database and
>was considering oracle on an ultra, until i checked the price
>and 2,000 dollars, no way. I have used mSQL and looked
>at mySQL and now am aware of postgres and have heard that it
>is the most robust and well used of the freeware databases.
>Is this correct? Also i am wondering about it's realibility,
>stability, scalability, etcetera? Can anyone point me in
>the right direction for this info. Also is there a web page
>or list of people running postgres, with their configurations,
>connections and what not. I would like to know that their
>are other people using postgres for commercial web sites.
>The whole company will depend on the database and so i just
>don't want to be the only person doing this. When i
>implemented mSQL for this things weren't nearly as important
>and performance and scalability weren't as essential.
>
>
> Any help, comments, advice would be greatly appreciated.
>
> Eric Enockson
>