Re: Shared memory errors during initdb in Mac OS X

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Siracusa <siracusa(at)mindspring(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Shared memory errors during initdb in Mac OS X
Date: 2004-03-22 21:02:54
Message-ID: 8106.1079989374@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

John Siracusa <siracusa(at)mindspring(dot)com> writes:
> and then restarted. Now it works, but I'm not sure if it was the change in
> settings or the restart that fixed it. Obviously I had to restart to make
> the changes take effect, but my theory before I bit the bullet and restarted
> was that some stale shared memory was lurking, making too little available
> for Postgres.

I was wondering about that as I read your message, but my recollection
is that you get a different kernel error code (not "Invalid argument")
if the request size would be legal by itself but is rejected due to
other pre-existing allocations. You might want to try deliberately
provoking such a situation and see what error you get.

> This leads to me next question: is there an equivalent to the ipcs command
> for Mac OS X?

Not that I've found. It's a very annoying omission :-(. I'm not sure
if Darwin is sufficiently BSD-ish that it would work to compile up ipcs
from one of the BSD distributions, but you could try ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jerry LeVan 2004-03-22 21:20:39 Re: Shared memory errors during initdb in Mac OS X
Previous Message Michael Chaney 2004-03-22 20:55:55 Re: PHP or JSP? That is the question.