From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Thomas T(dot) Thai" <tom(at)minnesota(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: first crash |
Date: | 2003-03-06 21:08:00 |
Message-ID: | 18145.1046984880@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Thomas T. Thai" <tom(at)minnesota(dot)com> writes:
> I had my first production crash today.
> PostgreSQL v7.3
> NetBSD/Alpha 1.6
Why are you not running 7.3.2?
> Is there anything I can do to help track down this issue?
Provide stack traces from the core dumps. If you're not getting core
dumps, you may need to set "ulimit -c unlimited" before launching the
postmaster. Also, keep in mind that the postmaster itself never does
chdir(), so it would try to dump core in whatever directory you are in
when you launch it. Make sure this directory is writable by postgres,
or you'll get no core...
Also, did you look to see if there is anything interesting in the
postmaster log? It could be that this was not a core dump but a panic
exit, in which case the postmaster would have written a complaint to the
log before exiting.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ericson Smith | 2003-03-06 21:15:48 | Sequential Scans |
Previous Message | Dennis Gearon | 2003-03-06 20:52:10 | Re: triggers |