Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] initdb fails to allocate shared memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] initdb fails to allocate shared memory
Date: 2010-08-25 19:28:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
I wrote:
> it appears from your report that OS X is also using ENOMEM when SHMALL
> is exceeded, which is not all that surprising because actually none of
> the spec-defined error codes cover SHMALL exhaustion.

A look into
confirms this:

	if ((user_ssize_t)(shm_committed + btoc(total_size)) > shminfo.shmall)
		return ENOMEM;

So this behavior is probably common among BSDen.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2010-08-25 19:39:19
Subject: Re: Python 2.7 deprecated the PyCObject API?
Previous:From: A.M.Date: 2010-08-25 19:18:03
Subject: new notify payload as string

pgsql-general by date

Next:From: wei725Date: 2010-08-25 19:29:21
Subject: How to convert a binary filed to an integer field?
Previous:From: bricklenDate: 2010-08-25 19:20:02
Subject: Re: unexpected message type 0x58 during COPY from stdin

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group