If there isn't any kernel panic (or other error message) displayed then I'd
bet it's a memory problem (it's almost certainly a hardware problem),
PostgreSQL is just triggering it (probably by using the damaged memory).
I've seen this happen before with other programs... Try switching out the
RAM and running the queries again..
-Mitch
----- Original Message -----
From: "Nils Zonneveld" <nils@casema.net>
To: <pgsql-general@postgresql.org>
Sent: Monday, September 25, 2000 2:23 PM
Subject: [GENERAL] more or less spontaneous reboots with Suse 6.4 /
Postgresql 7.0.2
> Hi all,
>
> I use Suse Linux 6.4 (kernel 2.2.14) and when I'm executing SQL
> statements in batch to postgresql (like: psql db < schema.sql) I have a
> fair chance that Linux reboots. No entries about the mishap are logged
> in the postgres logfile and neither in /var/log/messages. There's no
> telling when it exactly happens but when one of the statements contains
> an error the chance is really high that the system reboots.
>
> I have no idea if Postgres is to blame or the linux kernel. I have to
> admit that I'm still using the generic kernel, but I think it is a bit
> silly that a user process like postmaster could bring the whole server
down.
>
> If anyone has had a simulair experience and found a solution I would
> like to know about it.
>
> Thanks in advance,
>
> Nils Zonneveld
> --
> "Misschien is niets geheel waar, en zelfs dat niet"
> Multatuli (Eduard Douwes Dekker) - Idee 1
>