Tom Lane wrote:
Joe Barwell <[EMAIL PROTECTED]> writes:
I get the same result trying to initdb after rebooting, the
end of which is:
/Library/PostgreSQL8/data/base/1 ... FATAL: could not
create shared memory segment: Cannot allocate memory
DETAIL: Failed system call was shmget(key=2, size=1646592,
03600).
HINT: This error usually means that PostgreSQL's request
for a shared memory segment exceeded available memory or
swap space.
Hmph. That is definitely not a SHMMAX violation (you get "Invalid
argument" for that). AFAIK the only two causes are SHMALL violation
(which, since your SHMMAX and SHMALL are effectively the same, means
someone is already eating part of SHMALL); or that you actually have not
got enough RAM to allocate the shmem segment. Which does not seem real
probable, for a mere 1.6MB. So I'm thinking something somewhere is
allocating a shmem segment behind your back. Maybe those earlier
"failed" attempts actually did install a working Postgres server?
You should troll through the "ps" listing carefully.
Doesn't MacOSX install postgresql by default for one of their management
services?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
---------------------------(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
