From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Sigh, my old HPUX box is totally broken by DSM patch |
Date: | 2013-10-24 17:24:26 |
Message-ID: | 20131024172426.GD18793@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2013-10-24 13:13:23 -0400, Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> The above patch ignores SIGSYS throughout initdb. We could narrow the
> possible side-effects by only disabling SIGSYS around the shm_open call,
> but I'm not sure there's any value in that. It seems likely to me that
> the same kind of problem might pop up elsewhere in future, as we try
> to make use of other modern kernel facilities. In fact, I can foresee
> wanting to run the whole backend this way --- though I'm not proposing
> doing so today.
Why not? I don't see the advantage of looking for effects/problems of
such a chance twice.
I'd also much rather see a wrongly configured postgres fail to start
with a legible error message instead of it being killed by a signal.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-10-24 17:24:52 | Re: Sigh, my old HPUX box is totally broken by DSM patch |
Previous Message | ktm@rice.edu | 2013-10-24 17:19:29 | Re: Compression of full-page-writes |