Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA01960; Thu, 18 Mar 93 15:02:50 -0800
Date: Thu, 18 Mar 93 15:02:50 -0800
Message-Id: <9303182302.AA01960@postgres.Berkeley.EDU>
From: witr@rwwa.COM
Subject: Re: Core Dumps
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Content-Type: text
Content-Length: 786

> It is however a definite problem in SVR4 (actually sysv in general).
> In sysv when a signal handler is called, the signal is reset so that
> the handler no longer catches the signal (probably an attempt to
> defeat endless loops if an error occurs while in a handler.)

The identification of the problem is correct, but the solution
suggested is not sufficient to yeild a robust Postgres on SVR4.  What
I suggest (and what I did on my port) is to write a signal(2)
replacement as suggested by Stevens, and also change the
setjmp/longjmp to sigsetjmp/siglongjmp.  You must do *both* of these
things to get a reliable Postgres.

---
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA