Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BE5629FB2DC for ; Mon, 22 Jan 2007 13:27:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 77413-08 for ; Mon, 22 Jan 2007 13:27:11 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 7A9B89FB286 for ; Mon, 22 Jan 2007 13:27:11 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l0MHR6h18875; Mon, 22 Jan 2007 12:27:06 -0500 (EST) From: Bruce Momjian Message-Id: <200701221727.l0MHR6h18875@momjian.us> Subject: Re: server process (PID xxx) was terminated by signal In-Reply-To: <20070122164719.GI26006@alvh.no-ip.org> To: Alvaro Herrera Date: Mon, 22 Jan 2007 12:27:06 -0500 (EST) CC: Tom Lane , Achilleas Mantzios , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/200 X-Sequence-Number: 24356 Alvaro Herrera wrote: > Tom Lane wrote: > > Achilleas Mantzios writes: > > > In one of our remote pgsql 7.4.2 installations (no tcp/ip, no mgetty dialin > > > works always), i got the above message. > > > > Since you have not told us what the platform is, there is no way to > > guess what signal 7 means. Please look in its /usr/include/signal.h > > (or more likely, some sub-file that includes) to find out the symbolic > > name of the signal, and report that. > > kill -l is mandated by POSIX to return the list of signal names and > numbers. Is there no API to return the name of signals? I am looking for something like this on Win32 for exceptions and can't find it either. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +