From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Colin Stagner <cbs228(at)earthlink(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: PG crashes MacOS 10.3.4 |
Date: | 2004-07-29 16:38:26 |
Message-ID: | 15120.1091119106@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Colin Stagner <cbs228(at)earthlink(dot)net> writes:
> At random intervals that seem to vary by database uptime and usage, a
> COPY [table] FROM [file] statement involving maybe 20k - 80k rows
> (larger amounts of data than I usually work with, but nothing the
> server shouldn't be able to handle) will crash the machine. The screen
> freezes, except for the mouse which freezes after about 30 seconds, and
> the machine doesn't respond to keyboard or mouse input. Attempts to SSH
> into the machine fail-- its not just the GUI locking up. The machine
> must be cold-booted with the reset button.
As an unprivileged process, Postgres *cannot* crash the machine --- at
least not on sanely-written operating systems, and OS X qualifies. A
system-wide lockup is either a hardware fault or a kernel bug.
My money is on an intermittent hardware problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-07-29 17:07:51 | Re: [HACKERS] Point in Time Recovery |
Previous Message | Gaetano Mendola | 2004-07-29 16:29:10 | Re: replication and linux-ha? |