From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Grant Maxwell <grant(dot)maxwell(at)maxan(dot)com(dot)au> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: "show all" command crashes server *** FIXED *** |
Date: | 2009-09-14 00:24:30 |
Message-ID: | 26908.1252887870@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Grant Maxwell <grant(dot)maxwell(at)maxan(dot)com(dot)au> writes:
> The error was that if "show all" was run on this postgresql (version
> 8.3) server, postgres would crash and then recover.
> The postgres log showed:
> Sep 10 23:55:36 theconsole postgres[31118]: [4-1] 0: LOG: 00000:
> server process (PID 31145) was terminated by signal 11: Segmentation
> fault
> We had recently ( a month before) had installed splunk on the server.
> It was running ok
> The combination of splunk and other tasks running had pushed the
> memory too close.
> What we did not notice was that swap had been almost completely
> consumed - nasty
> We shut it all down, increased the memory (double) and voila -
> problem gone.
Hmm. A segfault in that case seems to indicate that something somewhere
is failing to check for a null result from malloc(). Which is a bug we
ought to fix. Is there any chance of getting a core dump stack trace
from one of those crashes?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Cory Isaacson | 2009-09-14 03:57:50 | Checkpoint request failed, permission denied |
Previous Message | Grant Maxwell | 2009-09-13 23:32:30 | Re: "show all" command crashes server *** FIXED *** |