| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brusser, Michael" <Michael(dot)Brusser(at)matrixone(dot)com> |
| Cc: | "Pgsql-Hackers (E-mail)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backend died |
| Date: | 2004-11-15 19:48:18 |
| Message-ID: | 10025.1100548098@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Brusser, Michael" <Michael(dot)Brusser(at)matrixone(dot)com> writes:
> Our customer running Postgres v. 7.3.2 reported a problem, occurring
> couple times a week on three different servers, all on Solaris 9.
> 2004-11-13 10:01:06 [10456] DEBUG: child process (pid 19285) was
> terminated by signal 10
SIGBUS iirc.
> What else should I look at?
Find out what query is causing the crash --- enable query logging if you
have no other way. And get a debugger stack trace from the core file
that the crashed backend left behind.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brusser, Michael | 2004-11-15 20:01:44 | Re: backend died |
| Previous Message | Brusser, Michael | 2004-11-15 19:30:39 | backend died |