From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Keary Suska <hierophant(at)pcisys(dot)net> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: semget: No space left on device |
Date: | 2003-05-10 03:25:01 |
Message-ID: | 3935.1052537101@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Keary Suska <hierophant(at)pcisys(dot)net> writes:
> I need to increase the max connections for my postgres installation but when
> I do I get the dreaded "semget: No space left on device" error. Where can I
> find information on the relationship between max connections and buffers and
> shared memory/semaphores?
You evidently need to raise SEMMNI: your setup is eating 127 of the 128
you have allowed.
It does seem odd that you have
------ Semaphore Status --------
used arrays = 127
allocated semaphores = 159
Postgres will normally allocate 17 semaphores per semaphore ID (a/k/a
semaphore array). It looks to me like some not-Postgres application has
chewed up 125 semaphore IDs to represent only one actual semaphore apiece.
Postgres took two more for 17 apiece, then choked trying to get a third.
What else are you running ... and have you complained to them about
their profligacy with semaphore IDs?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Keary Suska | 2003-05-10 05:31:48 | Re: semget: No space left on device |
Previous Message | Chris Palmer | 2003-05-09 23:47:38 | Unicode confusion |