{"id":1422,"date":"2018-01-19T19:22:49","date_gmt":"2018-01-19T19:22:49","guid":{"rendered":"http:\/\/goofy-trucks.flywheelsites.com\/optimizing-postgresql\/"},"modified":"2018-01-19T19:24:46","modified_gmt":"2018-01-19T19:24:46","slug":"optimizing-postgresql","status":"publish","type":"post","link":"https:\/\/phpbuilder.com\/optimizing-postgresql\/","title":{"rendered":"Optimizing Postgresql"},"content":{"rendered":"
\n
\n
By PHP Builder Staff<\/div>\n
on August 21, 2001<\/div>\n<\/p><\/div>\n
\n
\nEricson Smith<\/div>\n
\nFollowing Tim
\nPerdue’s excellent article on the comparison between MySQL
\nand Postgresql<\/a>, I decided to take a shot at installing and using this
\ndatabase. For most of our work I use MySQL and will continue to do so,
\nbecause of its ease of use and unrivaled select query speed, and also
\nbecause there is no point in trying to mess around with production
\nsystems that already work fine.<\/div>\n
\nBut some new projects suffered greatly from MySQL’s table locking
\nfeature when I needed to update data (which I do a lot). Here are my
\nadventures in setting up a Postgresql database server.<\/div>\n
\nOur configuration for a dedicated Postgresql server was:<\/div>\n
\n