Re: how good is PHP-PostgreSQL???

In article <39FE70D9.CB30095D@laopdr.com>, george@laopdr.com wrote: >> Here's my problem.. We're about to build a site like hitbox.com where >> there is a large amount of database required.. If say there is 100,000 >> users with >> 1000 page hits per day for each, and everything will be logged, you >> could >> imagine how huge this will be. I'm just so "nervous" (really, that's > Arnold, I wouldn't recommend postgres for this. Mysql is a much better > databse for reading but experiences problems when thatre are a lot of > write transaction to be done to be done. Having said that mysql doesn't > come with the rollback. It is where if part of a transaction fails, all I don't understand your recommendation here. From Arnolds description of his application it looks like what he's doing (logging) will involve a large amount of writing to the database, not reading. If this is the case then surely PostgreSQL is more naturally suited to the problem than MySQL which is (currently) stuck with table level locking on writes? > of the transaction is reveresed to the point where you stared the > transaction. MySQL does have transactions, you just have to specify that you want them when you create a table, at least that's what I gather from the docs...... In any case, I haven't taken either database near the figures that Arnold is talking about. The best thing to do, would probably be to knock up a prototype, then bang on it (with a bunch of clients running something like jmeter from the Apache group) and see how you fair. Then tune, then bang away again. Paul