Transactions on mysql vs postgresql

I have used both mysql and postgresql on several of my smaller sites. And it looks as though one is about to scale up dramatically. So I am pretty much going to have to pick one of the two and take it from there. Some small background: I like the "i am screwed but you can recover" ability of isamchk. I dislike the "this is a new version of postgres so you have to do a full dump." aspect of postgres. I have had trouble getting postgres to run out of the box. Especially with phpPgAdmin. Though I did get it running eventually. I will be using phpPgAdmin or phpMyAdmin as an administrator tool. I was tending towards postgresql because of transactions locking (there will be financial and inventory transactions taking place) but then I read that mysql-max had a form of transaction locking also. The reviews I have read seem rather ambigious on which of the two is superior. So I am asking for opinions. Is the transactions locking ability of mysql-max good enough to rely on? The basis of my sites at the moment use phplib style authentication which I do like (even if it is flaky on logouts). (Often I need to click the logout twice for it to fully commit.) I use an inc file for all format calls. And I am somehow going to figure out how to do my updates with some form of generic update function like I have my queries below.. include("table.inc"); // requires include_path to be functioning $db = new DB_Example; $db->query("select * from wsj"); $t = new Table; $t->heading = "on"; $t->show_result($db); page_close(); Thanks for the help. -- Dr. Roy F. Cabaniss Associate Professor of Business University of Arkansas Monticello http://cabanisspc.uamont.edu/~rcaban