Postgresql Leopard Gotchas →
After a fresh postgresql installation, initdb didn’t work until I reset the kern.sysv.shmall and kern.sysv.shmmax:
sudo sysctl -w kern.sysv.shmmax=134217728
sudo sysctl -w kern.sysv.shmall=65536
some problems, solutions, and other stuff i've encountered as a web developer
After a fresh postgresql installation, initdb didn’t work until I reset the kern.sysv.shmall and kern.sysv.shmmax:
sudo sysctl -w kern.sysv.shmmax=134217728
sudo sysctl -w kern.sysv.shmall=65536
I just received the company-issued MacBook and it runs Leopard. I had to install MySQL and PostgreSQL and the Ruby Gems, and ultimately, had to encounter some problems. haha
I use MacPorts for most of the development software, Postgres, subversion, git, etc. I encountered problems in running the postgres server, most of the difficulty came from PGDATA unset in postgres user. Anyway, I was able to resolve this by not using PGDATA and include the whole path of the db when invoking pg_ctl.
MySQL. I just downloaded the dmg from the MySQL site. I was unable to run the server when I attempted to install it using MacPorts, so I just used the binary.
For the postgres and mysql gems, the only thing I missed other than the —with-pgsql-lib-dir, —with-pgsql-include-dir, and —with-mysql-dir was the env ARCHFLAGS=”-arch i386” when invoking the gem install. For example,
sudo env ARCHFLAGS=”-arch i386” gem install mysql — —with-mysql-dir=/usr/local/mysql