![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
/test/regress/./tmp_check/data/base/1 ... FATAL: could not create shared memory segment: Cannot allocate memory DETAIL: Failed system call was shmget(key=2, size=1163264, 03600). |
#2
| |||
| |||
|
|
I just downloaded and compiled PostgreSQL 8.0 beta 3. The directory and files are all owned by the "postgres" user, and I compiled as that user. I configured with: ./configure --prefix=/sw --with-tcl --with-python --with-libs=/sw/lib/ --with-includes=/sw/include/ (/sw is the root of the "fink" hierarchy, analogous in some ways to the traditional /usr/local path.) The "make check" log included the following: creating template1 database in /Users/reuven/Downloads/postgresql-8.0.0beta3/src /test/regress/./tmp_check/data/base/1 ... FATAL: could not create shared memory segment: Cannot allocate memory DETAIL: Failed system call was shmget(key=2, size=1163264, 03600). HINT: This error usually means that PostgreSQL's request for a shared memory se gment exceeded available memory or swap space. To reduce the request size (curre ntly 1163264 bytes), reduce PostgreSQL's shared_buffers parameter (currently 50) and/or its max_connections parameter (currently 10). The PostgreSQL documentation contains more information about shared memo ry configuration. child process exited with exit code 1 initdb: failed initdb: data directory "/Users/reuven/Downloads/postgresql-8.0.0beta3/src/test/r egress/./tmp_check/data" not removed at user's request Reuven ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |
#3
| |||
| |||
|
|
OS X has an unreasonably small limit on shared memory size; if you don't raise it (IIRC you can do this in /etc/rc) then you don't get to have more than one postmaster at a time. OK, I see what you're talking about from looking in /etc/rc. You might |
![]() |
| Thread Tools | |
| Display Modes | |
| |