Search Postgresql Archives

Re: initdb fails to allocate shared memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"A.M." <agentm@xxxxxxxxxxxxxxxxxxxxx> writes:
> Then it seems that the error reporting could be improved to not mention "shared_buffers" and "max_connections" neither of 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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux