Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6 - Mailing list pgsql-hackers

From Kris Jurka
Subject Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6
Date
Msg-id Pine.BSO.4.56.0411141958040.32108@leary.csoft.net
Whole thread Raw
In response to Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

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 you think 31 is the failure case your 
thinking of or whether 31 might help.

Kris Jurka


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6
Next
From: Tom Lane
Date:
Subject: Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6