i use postgresql at work and the reson we chose it baove mysql (which i also
use for developement @ home) was scalability.
from our investigations mysql does not scale well wehn having 100+ users.
BUT before i start a pointless debate on the merits of either both DB's seem
to have 'converged' over thelast year or so.
the db we run at work has 500K+ records and runs very quickly. i'm not so
sure mysql would perform like this for the 100+ users that are connected
most of the time.
postgresql has a better feel to it as well, and has better SQL support
(inner selects are 'mising' in mysql)
"Miles Thompson" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Are you querying on indexed fields? That's the key to speed; check the
> MySQL docs on how it uses indexes. 20k records is not a large database.
> At 04:06 PM 8/24/01 +0800, Lester June Cabrera wrote:
> >We've been using MySQL for 2 years now in all the PHP systems we have
> >developed for our clients. We're thinking of using PostgreSQL now. What
> >your experience with PostgreSQL? Any comments? The reason why we want to
> >shift is because we have encountered some problems with one of our
> >databases whose table contains more than 20K records. Somehow, it took so
> >long to query the database. Is PosgtreSQL a good substitute? We're
> >expecting a million records for our new project.
> >PHP Database Mailing List (http://www.php.net/)
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >To contact the list administrators, e-mail: [EMAIL PROTECTED]
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]