Date: Sun, 7 Jul 1996 14:15:03 -0400 (EDT) From: "Marc G. Fournier" <scrappy@ki.net> To: current@freebsd.org Subject: Shared Memory Buffers ... Message-ID: <Pine.NEB.3.94.960707140526.11612A-100000@ki.net>
next in thread | raw e-mail | index | archive | help
Hi...
Back again with another question...
I'm running Postgres95 1.01 under FreeBSD 2.2-current pretty
much problem free, except every once in a while I get a "backend crash"
due to shared memory corruption (sorry, don't have the exact error message
to include)
Now, those on the Postgres95 mailing list suggestion starting
up the postmaster daemon with -B 1024, which is:
-B n_buffers
n_buffers is the number of shared-memory buffers for
the postmaster to allocate and manage for the backend
server processes that it starts. This value defaults
to 64.
Except, if I try, I get:
postgres@zeus> bin/postmaster -B 1024 -S
IpcMemoryCreate: memKey=155356396 , size=8697560 , permission=384IpcMemoryCreate: shmget(..., create, ...) failed: Invalid argument
If I do it as -B 64, it works, but then again, that's the default
setting...
As I know absolutely zilch about semaphores and shared memory,
can someone tell me what is wrong here? Is it a coding problem inside
of the postgres95 server (which I would assume would mean that -B 64
shouldn't work either)? Is it a setting I have to increase in my
kernel? Or is it associated with the 'datasize' value that the limit
command shows me?
I've checked the handbook, FAQ and about every other resource I
could find @ www.freebsd.org, but can't even find any references to
shared memoryy/SYSV* related settings :(
Marc G. Fournier scrappy@ki.net
Systems Administrator @ ki.net scrappy@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.94.960707140526.11612A-100000>