This web developer for both internet and intranet applications, who does
both connectionless and simulated connection oriented applications, uses
PostgreSQL WHERE EVER POSSIBLE. If I ever have issues with load, there are
much better ways of getting performance then choosing a less capable
database for its trimness (eg horsepower and memory are cheap, dedicated
servers are cheap, and better table design/layout/indexes usually will fix
ANY databases slowness where mass volume is not the issue).
I train all my programmers on ONE db architecture, I have to maintain only
ONE db architecture on all my servers, and the db I have chosen does
everything that even my most complex job needs to do. (Now that 7.2.1
supports OUTER JOINS).
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of
> Thomas Lockhart
> Sent: Friday, July 12, 2002 10:05 AM
> To: Curt Sampson
> Cc: builder; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] MySQL vs. PostgreSQL
>
>
> ...
> > Not many Web developers use PostgreSQL because they feel that
> > the additional features degrade performance.
>
> "Not many web developers" is a completely subjective
> statement which has
> no basis in fact. How many is "not many"? Is that two? One
> hundred? Two
> million? Twenty million?
>
> How many is "many web developers"? Must be more than "not many", eh?
> Probably can't narrow it down much beyond that :/
>
> Hmm. Given the proven performance scaling benefits from Postgres, one
> could also say "not many web developers feel that their applications
> need to scale beyond 5 simultaneous users". Or "not many web
> developers
> need transaction-enabled databases", or ???
>
> - Thomas
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo@postgresql.org
>