3 ms·

If you don't configure your shmmax first, you might have a problem when tweaking the memory setting in postgresql.conf. Relevant doc: http://www.postgresql.org

• rosser 14y ago
  TL; DR: Postgres will just fail to start if shmmax is too small, and the logs will reflect that. On Linux, you'd say: # sysctl -w kernel.shmmax=N Where N is the desired maximum shm segment size. (You'll also want to increase shmall, to accommodate shmmax, and any other shared memory requirements you may have.) EDIT: Of course, to make the change persist across reboots, you'll also want to add it to /etc/sysctl.conf. I've forgotten that part more than just in this comment...
  • stefantalpalaru 14y ago
    Try this strategy instead of using sysctl to set individual values: - edit /etc/sysctl.conf - run "sysctl -p"
    • james4k 14y ago
      Yes, definitely. I just learned about -p recently, and had been editing the config AND running sysctl -w for way too long.