[ale] project help - postgres or mysql?

[Jeff Hubbs]

If I were in your shoes, I would use PostGreSQL unless I needed
"ludicrous speed" and was for some reason unable to throw hardware at
the problem or had already done so and still wanted to go faster.

- Jeff

On Thu, 2003-01-02 at 14:05, John Wells wrote:
> Project I'm ramping up on will involve porting a microcrap sql server db
> to either postgres or mysql.  No stored procedures on the sql server side,
> thankfully.  Just tables and indexes.
> 
> The current db has a total of 227,626 rows, 249 tables.  Only 4 tables are
> over 10000...most are either in the 10s or hundreds.  Largest table is
> 89890.
> (for list of counts, see http://sourceillustrated.com/projects/tblcnt.html).
> 
> My initial thoughts are to use MySql, but wanted to put the question forth
> to the list.  I think mysql would have no problem handling this size, but
> want to be sure.
> 
> Would postgres be a better choice?
> 
> Thanks!
> 
> John
> 
> 
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale


_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale