Re: [HACKERS] IpcSemaphoreLock/Unlock and proc_exit on 7.2.6

2004-11-14 Thread Tom Lane
Kris Jurka <[EMAIL PROTECTED]> writes: > On Sun, 14 Nov 2004, Tom Lane wrote: >> Is your current value one less than a multiple of 16, by any chance? > Currently 32. It is unclear whether you think 31 is the failure case your > thinking of or whether 31 might help. No, 32 is actually the best c

Re: [HACKERS] IpcSemaphoreLock/Unlock and proc_exit on 7.2.6

2004-11-14 Thread Kris Jurka
On Sun, 14 Nov 2004, Tom Lane wrote: > The comment in ProcGetNewSemIdAndNum suggests that you might be able to > suppress the problem in 7.2 by using a different max_connections value. > Is your current value one less than a multiple of 16, by any chance? > Currently 32. It is unclear whether

Re: [HACKERS] IpcSemaphoreLock/Unlock and proc_exit on 7.2.6

2004-11-14 Thread Tom Lane
Kris Jurka <[EMAIL PROTECTED]> writes: > I have an underpowered server running 7.2.6 that backs a website which > occasionally gets hit by a bunch of traffic and starts firing off "FATAL > 1: Sorry, too many clients already" messages. This is all as expected, > but sometimes it just crashes. I h

[HACKERS] IpcSemaphoreLock/Unlock and proc_exit on 7.2.6

2004-11-13 Thread Kris Jurka
I have an underpowered server running 7.2.6 that backs a website which occasionally gets hit by a bunch of traffic and starts firing off "FATAL 1: Sorry, too many clients already" messages. This is all as expected, but sometimes it just crashes. I had no clue what was going on until I checked t