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

From Bruce Momjian
Subject Re: [HACKERS] Re: Max backend limits cleaned up
Date
Msg-id 199902211927.OAA19476@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: Max backend limits cleaned up  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Re: Max backend limits cleaned up
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.

Sure.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

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