Just a final note:
Changing shmall did fix the problem. Thanks to everyone for the help.
the final working settings i used are:
kern.sysv.shmmax=4194304
kern.sysv.shmmin=1
kern.sysv.shmmni=32
kern.sysv.shmseg=8
kern.sysv.shmall=4194304
I'm wondering how I managed to get it to work before, witho
On May 7, 2007, at 9:11 AM, Tom Lane wrote:
I believe BTW that you
need to do "sudo ipcs -a" to be sure of seeing everything; otherwise
OS X's ipcs silently doesn't tell you about segments your userid
doesn't
have access to.
Actually, it seems that you don't get anything back when ipcs is ru
Jim Nasby <[EMAIL PROTECTED]> writes:
> I'm guessing the issue here is shmall, which I believe is limiting
> you to 4MB of shared memory. Is there *anything* using shared memory
> in the ipcs report?
Right, it looks like shmall is the problem. I believe BTW that you
need to do "sudo ipcs -a"
When you increase shmmax, you need to increase shmall as well. Max is the
largest single allocation allowed, in bytes. All is the total SysV shared
memory available to all processes, in pages. (I think...)
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
---
On May 7, 2007, at 6:19 AM, Christopher S Martin wrote:
No .pid files found in the data directory.
The ipcs output doesn't list anything owned by the postgres user,
or by root.
I'm guessing the issue here is shmall, which I believe is limiting
you to 4MB of shared memory. Is there *anything
Bah, evil google interface. My reply was ment for the list.
On 5/7/07, Isak Hansen <[EMAIL PROTECTED]> wrote:
On 5/7/07, Christopher S Martin <[EMAIL PROTECTED]> wrote:
> sysctl -a reveals the following:
> kern.sysv.shmmax: 12582912
Maximum size of shared memory segment (afaik bytes - needs to
t; > > > > >
> > > > > > They didn't take any memory out of the machine. AS for memory
> cache
> > > > > > parameters, I'm don't know about that. How would I go checking
> for
> > > > > > that
> > > > >
> > > > > Thanks,
> > > > > Chris
> > > > >
> > > > > On 5/6/07, Martin Gainty < [EMAIL PROTECTED] > wrote:
> > > > > > if you're getting memory errors then a guess would be did they
take
> > > if you're getting memory errors then a guess would be did they
take
> out
> > > any
> > > > > memory out of your machine or perhaps did they change your
memory
> cache
> > > > > parameters???
> > > > > Martin
> &
t; This email message and any files transmitted with it contain
> > confidential
> > > > information intended only for the person(s) to whom this email
message
> > is
> > > > addressed. If you have received this email message in error, please
> > notify
> > &
ail message in error, please
> notify
> > > the sender immediately by telephone or email and destroy the
original
> > > message without making a copy. Thank you.
> > >
> > > - Original Message -
> > > From: "Christopher S Martin" <[EMAIL P
his email message
is
> > addressed. If you have received this email message in error, please
notify
> > the sender immediately by telephone or email and destroy the original
> > message without making a copy. Thank you.
> >
> > ----- Original Message -
> >
d destroy the original
> message without making a copy. Thank you.
>
> - Original Message -
> From: "Christopher S Martin" <[EMAIL PROTECTED]>
> To:
> Sent: Sunday, May 06, 2007 3:07 PM
> Subject: [GENERAL] shmget fails on OS X with proper settings
>
>
> >
First off, use sysctl to see what values are actually being set:
sysctl -a | grep kern.sysv.
The if they're not what you think they should be, tell us exactly how you're
trying to set them.
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
"Christopher S Martin" <[EMAIL PROTECTED]> writes:
> I was previous running postgres 8.2.1 on my OS X 10.4.9 laptop with no
> problems.
> After I sent it to apple care, I found that I can no longer start the
> postmaster daemon. When I try, I receive the standard shmget failed
> error message:
u have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: "Christopher S Martin" <[EMAIL PROTECTED]>
To:
Sent: Sunday, May 06, 2007 3:0
IL PROTECTED]>
To:
Sent: Sunday, May 06, 2007 3:07 PM
Subject: [GENERAL] shmget fails on OS X with proper settings
Hi to the list, its my first post.
I was previous running postgres 8.2.1 on my OS X 10.4.9 laptop with no
problems.
After I sent it to apple care, I found that I can no longer
Hi to the list, its my first post.
I was previous running postgres 8.2.1 on my OS X 10.4.9 laptop with no problems.
After I sent it to apple care, I found that I can no longer start the
postmaster daemon. When I try, I receive the standard shmget failed
error message:
FATAL: could not create
18 matches
Mail list logo
