Re: [postgres no lnger launches

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Reichstadt <lxr(at)mac(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [postgres no lnger launches
Date: 2012-06-03 23:16:36
Message-ID: 16607.1338765396@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alexander Reichstadt <lxr(at)mac(dot)com> writes:
>> So sure enough that process claimed to might be starting does not end up being a process. Where do I look for what's actually going on?

In the postmaster log ...

>> This is the log output:
>> 04.06.12 00:26:29,792 com.edb.launchd.postgresql-9.1: If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.

You seem to have trimmed off the useful part of this error message, but
I'm going to take a wild guess that what is happening is (a) you have
another postmaster running someplace, and (b) it is chewing up all the
allowed space for shared memory. If you have not mucked with OSX's
default shared-memory limits then there is only enough room to run one
postmaster at a time. The trouble with this theory is that the other
postmaster probably ought to be visible in ps output; I'm not sure why
it might not be. Anyway, try running "ipcs" to see if any SysV shared
memory or semaphores are active. If there are any, it's a pretty good
tip that there's a Postgres running somewhere.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Reichstadt 2012-06-03 23:35:44 [Solved] Re: [postgres no lnger launches
Previous Message Alexander Reichstadt 2012-06-03 23:03:46 Re: [postgres no lnger launches