Re: initdb fails to allocate shared memory - Mailing list pgsql-general

From Tom Lane
Subject Re: initdb fails to allocate shared memory
Date
Msg-id 21345.1282753700@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb fails to allocate shared memory  ("A.M." <agentm@themactionfaction.com>)
Responses Re: initdb fails to allocate shared memory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
"A.M." <agentm@themactionfaction.com> writes:
> Then it seems that the error reporting could be improved to not mention "shared_buffers" and "max_connections"
neitherof which I can touch during initdb. 

The error has to be phrased to cover the case where you hit it after
initdb.  It would be quite unhelpful to *not* mention those settings.

However, it's odd that you got this variant of the HINT and not the one
that suggests increasing SHMMAX.  Looking at the code, that means that
shmget returned ENOMEM, not EINVAL, which surprises me.  What did you
have your kernel settings at?  Could we see the output of
    sysctl -a | grep sysv

            regards, tom lane

pgsql-general by date:

Previous
From: Eric Comeau
Date:
Subject: Re: Feature proposal
Next
From: Tom Lane
Date:
Subject: Re: initdb fails to allocate shared memory