Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD
Date
Msg-id 30949.1466608503@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD  (Maxim Sobolev <sobomax@freebsd.org>)
Responses Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD  (Maxim Sobolev <sobomax@sippysoft.com>)
List pgsql-bugs
Maxim Sobolev <sobomax@freebsd.org> writes:
> Tom, on the related note on merits of SYSV semaphores vs. POSIX the
> handling of SYSV semaphore shortage in PG is, uggh, awful. The whole server
> crashes (abort()s), bumping into that on production box is not fun at all
> and it's particularly easy since the resource is severely constrained by
> default. Ideally it should just deny the particular connection request.

This seems like nonsense, because those are acquired once at postmaster
startup, not per connection.  You will need to decrease max_connections
to start successfully in a resource-constrained system, but the same is
true of other resource limits.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump doesn't dump new objects created in schemas from extensions
Next
From: Tom Lane
Date:
Subject: Re: BUG #14208: Inconsistent code modification - 3