From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Scott Goodwin <scott(at)scottg(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 7.4RC1 crashes on Panther |
Date: | 2003-11-04 21:48:27 |
Message-ID: | 25288.1067982507@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Scott Goodwin <scott(at)scottg(dot)net> writes:
> FATAL: could not create shared memory segment: Cannot allocate memory
> Here's the code that triggers it:
> create function pltcl_call_handler() RETURNS LANGUAGE_HANDLER
> as 'pltcl.so' language 'c';
I don't think so. That's a startup failure; it can not be triggered by
executing a SQL command, because if the postmaster is alive enough to
accept a SQL command in the first place, it's already gotten past
creation of the shared memory segment.
> Not sure whether this is a PostgreSQL problem or a Mac OS 10.3 problem,
It's a user problem. If you're going to run multiple
shared-memory-using applications, it's up to you to adjust the kernel
limit or the per-application requests to fit. I can't tell from this
what other app is using shared memory, though. Are you trying to start
more than one postmaster? If not, see whether OS X provides "ipcs" ---
that would give you some data about what shared-memory requests are
already present in the system.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Siegmar | 2003-11-05 16:08:58 | psql client 7.4RC1 completion bug |
Previous Message | Tomas Szepe | 2003-11-04 17:55:53 | Re: Repeatedly breaking indexes |