Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Moving from mysql to postgres 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I frequently have this conversation with Pg boosters who just won't recognize how annoying the initial setup for Pg is vs. the setup for MySQL. It's a fine database, and the auth system is powerful, but it's pretty obvious why newbies find MySQL easier to get going with.

    • I agree that installation is one of PG's weak areas, and I think part of the reason here is the way it's packaged on many distros. On Gentoo Linux, I can run 'emerge postgresql', followed by 'ebuild postgresql-8.1.3.ebuild config' and it takes care of creating a postgres user, creating a postgres database, and initializing the database. Doing this process manually (which is the case for many distributions) is tedious and probably turns off some users. If you have a reasonable sized database you'll also need to set the kernel shared memory max (kernel.shmmax).

      Mysql is admittedly easier to get going with. On most rpm based distributions I just type 'rpm -ivh mysql...rpm', then 'mysql' and I'm off to the races.

      I've had pretty good luck with the PG documentation though, and whenever I can't find something there I pop onto #postgresql on irc.freenode.net and I can get questions answered right away. Maybe that's because I'm more familiar with it though.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.