Re: [HACKERS] Reducing sema usage (was Postmaster dies with many child processes) - Mailing list pgsql-hackers

From Vadim Mikheev
Subject Re: [HACKERS] Reducing sema usage (was Postmaster dies with many child processes)
Date
Msg-id 36B514B1.9D5BCA8F@krs.ru
Whole thread Raw
In response to Reducing sema usage (was Postmaster dies with many child processes)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Thomas Reinke
Date:
Subject: Table exists, but not accessible?
Next
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] READ COMMITTED isolevel is implemented ...