Grant Maxwell <grant.maxw...@maxan.com.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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
