Tom Lane wrote:
>
> I said:
> > Another thing we ought to look at is changing the use of semaphores so
> > that Postgres uses a fixed number of semaphores, not a number that
> > increases as more and more backends are started. Kernels are
> > traditionally configured with very low limits for the SysV IPC
> > resources, so having a big appetite for semaphores is a Bad Thing.
>
...
>
> Any thoughts about which way to jump? I'm sort of inclined to take
> the simpler approach myself...
Could we use sigpause (or something like this) to block
and some signal to wake up?
Vadim