Search Postgresql Archives

Re: DB terminating

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks.  I altered the log log_statements and added the PID to the
log_line_prefix.  I have uploaded the log.  Forgive me if I'm missing
something obvious here, but I do not see that PID referenced elsewhere.  Is
there a a "crash report" somewhere or is that just these logs?

Thank you.
Scott



Tom Lane-2 wrote:
> 
> Scott Felt <scott.felt@xxxxxxxxx> writes:
>> Hello.  I have been having an issue with a database.  The logs
>> consistently
>> show this: 
> 
>> 2009-11-17 16:03:55 ESTLOG:  00000: server process (PID 9644) exited with
>> exit code 128 
> 
> This looks like a fairly garden-variety backend crash, but with only
> this much information there's no way to identify the cause.  You might
> try setting log_statements = all and see if there's any consistency in
> what the process was doing just before it crashed.  (You'd need to add
> PID to log_line_prefix so you could associate the log entries with the
> crash report.)
> 
> 			regards, tom lane
> 
> -- 
> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
> 
> 

-- 
View this message in context: http://old.nabble.com/DB-terminating-tp26412532p26630488.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux