When you switch to pg, you will be able to move some/lots? of your code into the database as views, stored procedures, triggers etc... So keep that in mind while working in MySQL, as you will definitely need a different approach.I will look into some of the suggestions you have made, the problem is that I can't do large scale optimization at the moment because I am still adding features to the site. I just wonder if the best mode of attack would be switching back to mysql until I have added all of the necessary features, optimizing the queries and code there, and then switching back to pg at a later date.
I inherited a site that had very database-hungry pages, and started using stored procs and triggers to automate some of the jobs (like updates and such) in the database, instead of making the webserver manually send the instructions across the wire. If you plan on taking this approach then you should get your app into pg sooner than later...
-- Mitch, wondering about 12 packs?
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
