The best thing is to fix the OS' ridiculously small shmem limits.
I've got this in /etc/sysctl.conf:
kern.sysv.shmmax=33554432
kern.sysv.shmmin=1
kern.sysv.shmmni=32
kern.sysv.shmseg=8
kern.sysv.shmall=8192
Dependency on the available RAM?
and on a production DB you'd probably want shmmax and shmall
a good bit higher.
Don't forget to reboot after changing settings. Also, a
"sysctl -a | grep shm" is a good idea to make sure it "took";
OS X is infamously picky about these settings.
regards, tom lane
A Macnerd as a core developer of Postgres? :-)
Sincerely,
Wolfgang Keller
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
