From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@postgresql.org
Subject: server process (PID xxx) was terminated by signal 7
Date: Mon, 22 Jan 2007 13:12:04 +0200
Message-ID: <200701221312.04840.achill@matrix.gatewaynet.com> (raw)
In-Reply-To: <20070122105038.805CA19F306@smtp07l.fasthosts.co.uk>
References: <20070122105038.805CA19F306@smtp07l.fasthosts.co.uk>
In one of our remote pgsql 7.4.2 installations (no tcp/ip, no mgetty dialin
works always), i got the above message.
The pgsql server restarted right away, but in the meantime a significant cron
job that just hapened to be executed between SIG7 and start, failed, and so
that triggered the investigation.
Could you think of a reason for this "signal 7" caught by the pgsql server?
Memory or other HW problem maybe?
Thank you.
--
Achilleas Mantzios
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: achill@matrix.gatewaynet.com, pgsql-admin@postgresql.org
Subject: Re: server process (PID xxx) was terminated by signal 7
In-Reply-To: <200701221312.04840.achill@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox