| From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | server process (PID xxx) was terminated by signal 7 |
| Date: | 2007-01-22 11:12:04 |
| Message-ID: | 200701221312.04840.achill@matrix.gatewaynet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-patches pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandre Becquereau | 2007-01-22 11:20:07 | Startup problem |
| Previous Message | Simon Kinsella | 2007-01-22 10:50:15 | FW: Possible to emulate pre-8.2 behaviour of SET CONSTRAINTS? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-01-22 13:06:53 | Re: [PATCHES] pg_standby |
| Previous Message | Simon Kinsella | 2007-01-22 10:50:15 | FW: Possible to emulate pre-8.2 behaviour of SET CONSTRAINTS? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-22 16:01:56 | Re: server process (PID xxx) was terminated by signal 7 |
| Previous Message | Simon Kinsella | 2007-01-22 10:50:15 | FW: Possible to emulate pre-8.2 behaviour of SET CONSTRAINTS? |