| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: Max backend limits cleaned up |
| Date: | 1999-02-21 18:43:47 |
| Message-ID: | 1285.919622627@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-02-21 18:58:04 | Anyone understand shared-memory space usage? |
| Previous Message | Bruce Momjian | 1999-02-21 03:59:12 | Re: [HACKERS] Re: Max backend limits cleaned up |