I have asked Apple about using a saner default for shmmax, but a few
more complaints in their bug system wouldn't hurt.
I suspect it won't help, since their official position is already don't use
shmget, use mmap instead...
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303)
Scott Ribe [EMAIL PROTECTED] writes:
I have asked Apple about using a saner default for shmmax, but a few
more complaints in their bug system wouldn't hurt.
I suspect it won't help, since their official position is already don't use
shmget, use mmap instead...
Given that they have improved
Given that they have improved their SysV IPC support steadily over the
past few Darwin releases, I don't see why you'd expect them to not be
willing to do this. Having a larger default limit costs them *zero* if
the feature is not used, so what's the objection?
The objection would be
Maybe this is a server vs normal OS X issue. I am postgres on a
normal iMac 10.3.5 with no problems, but this is just a developent box
so I don't need the server version. All of the servers that I run are
Linux/FreeBSD. I don't have access to a Mac server, if I did I would
test this myself.
I have a couple users trying to install Postgres on OS X. To the best
of my knowledge, both of them are using 7.4.5/10.3.5, and got identical
errors while trying to init the database:
Reducing the shared buffers didn't help.
Any thoughts would be appreciated.
Jeffrey Melloy
[EMAIL PROTECTED]
On Thu, 2004-09-30 at 13:49, Jeffrey Melloy wrote:
I have a couple users trying to install Postgres on OS X. To the best
of my knowledge, both of them are using 7.4.5/10.3.5, and got identical
errors while trying to init the database:
Have you tried the suggestions in the documentation?
Tom Lane wrote:
Jeffrey Melloy [EMAIL PROTECTED] writes:
I have a couple users trying to install Postgres on OS X. To the best
of my knowledge, both of them are using 7.4.5/10.3.5, and got identical
errors while trying to init the database:
They need to increase the system's shmmax
