Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6

From: Kris Jurka <books(at)ejurka(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6
Date: 2004-11-15 01:04:45
Message-ID: Pine.BSO.4.56.0411141958040.32108@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-11-15 01:10:06 Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6
Previous Message Tom Lane 2004-11-15 00:18:22 Re: IpcSemaphoreLock/Unlock and proc_exit on 7.2.6