> "Brusser, Michael" <[EMAIL PROTECTED]> 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
==================================================
The log-statements option was already enabled,
here's what I see prior to the crash:
2004-11-13 09:49:46 [10876] DEBUG: StartTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: SELECT SUM(C0),SUM(C1),SUM(C2),SUM(C3),SUM(C4),SUM(C5),SUM(C6),SUM(C7),SUM(C8),SUM(C9)
,SUM(C10) FROM cache_refreshes
2004-11-13 09:49:46 [10876] LOG: query: SELECT SUM(C0),SUM(C1),SUM(C2),SUM(C3),SUM(C4),SUM(C5),SUM(C6),SUM(C7),SUM(C8),SUM(C9),SUM
(C10) FROM cache_refreshes
2004-11-13 09:49:46 [10876] DEBUG: CommitTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: SELECT SUM(C0),SUM(C1),SUM(C2),SUM(C3),SUM(C4),SUM(C5),SUM(C6),SUM(C7),SUM(C8),SUM(C9)
,SUM(C10) FROM cache_refreshes
2004-11-13 09:49:46 [10876] DEBUG: StartTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: commit
2004-11-13 09:49:46 [10876] LOG: query: commit
2004-11-13 09:49:46 [10876] DEBUG: CommitTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: commit
2004-11-13 09:49:46 [10876] DEBUG: StartTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: begin
2004-11-13 09:49:46 [10876] LOG: query: begin
2004-11-13 09:49:46 [10876] DEBUG: CommitTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: begin
2004-11-13 09:49:46 [10876] DEBUG: StartTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: commit
2004-11-13 09:49:46 [10876] LOG: query: commit
2004-11-13 09:49:46 [10876] DEBUG: CommitTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: commit
2004-11-13 09:49:46 [10876] DEBUG: StartTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: begin
2004-11-13 09:49:46 [10876] LOG: query: begin
2004-11-13 09:49:46 [10876] DEBUG: CommitTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: begin
2004-11-13 09:49:46 [10876] DEBUG: StartTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: commit
2004-11-13 09:49:46 [10876] LOG: query: commit
2004-11-13 09:49:46 [10876] DEBUG: CommitTransactionCommand
2004-11-13 09:49:46 [10876] LOG: statement: commit
2004-11-13 09:54:21 [10456] DEBUG: child process (pid 19282) exited with exit code 0
2004-11-13 10:01:06 [10456] DEBUG: child process (pid 19285) was terminated by signal 10
2004-11-13 10:01:06 [10456] LOG: server process (pid 19285) was terminated by signal 10
2004-11-13 10:01:06 [10456] LOG: terminating any other active server processes
2004-11-13 10:01:06 [10456] DEBUG: CleanupProc: sending SIGQUIT to process 10876
... ... ...
The same app. is running for other customers, seemingly steady...
I will ask for the core file.
This is a brand new machine. Is it likely that a bad memory chip may cause this?
Thank you,
Mike
