| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Maxim Sobolev <sobomax(at)freebsd(dot)org> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Konstantin Belousov <kib(at)freebsd(dot)org> |
| Subject: | Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD |
| Date: | 2016-06-22 15:15:03 |
| Message-ID: | 30949.1466608503@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Maxim Sobolev <sobomax(at)freebsd(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-22 15:45:16 | Re: BUG #14208: Inconsistent code modification - 3 |
| Previous Message | Tom Lane | 2016-06-22 15:12:06 | Re: pg_dump doesn't dump new objects created in schemas from extensions |