Re: [HACKERS] Re: Max backend limits cleaned up - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Re: Max backend limits cleaned up
Date
Msg-id 1285.919622627@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: Max backend limits cleaned up  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Re: Max backend limits cleaned up  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] Re: Max backend limits cleaned up  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] Re: Max backend limits cleaned up  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <maillist@candle.pha.pa.us> writes:
>> 5. Allocation of semaphores and shared memory is now based on
>> -N switch value (default or specified) rather than the MAXBACKENDS
>> constant.

> sgml and man documenation updates, right?  Or should I do it?

I put something into the docs last night in the places where configure
and postmaster switches are described.

I am thinking, though, that we also ought to have FAQ entries under
headings like:
I get "IpcSemaphoreCreate: semget failed (No space left on device)"when I try to start the postmaster
I get 'Sorry, too many clients already' when trying to connect

If you like, I'll try to write up a first cut at these.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: Max backend limits cleaned up
Next
From: Tom Lane
Date:
Subject: Anyone understand shared-memory space usage?