From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Doug Roberts <h205881(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Postgres Crashing |
Date: | 2020-02-03 22:28:13 |
Message-ID: | 31245.1580768893@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Doug Roberts <h205881(at)gmail(dot)com> writes:
> I'm having an issue where a process in Postgres is crashing and cause the
> server to go into recovery mode.
Can you reduce this to a self-contained test case for others to try?
If not, you'll have to do the initial investigation yourself.
A stack trace from the crash would be pretty helpful:
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
We could also use all the standard details suggested in
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
most notably, exactly which PG version is this?
> I'm getting the following errors in the log.
Unfortunately, this is pretty useless, since you only quoted the part
of the log after the problem was detected.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-02-03 22:34:46 | Re: Postgres Crashing |
Previous Message | Adrian Klaver | 2020-02-03 21:49:06 | Re: Postgres Crashing |