| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | jack <jack4pg(at)a7q(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: constant crashing |
| Date: | 2024-04-14 17:13:38 |
| Message-ID: | 512139.1713114818@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 4/14/24 09:20, jack wrote:
>> The full error reads:
>> server closed the connection expectantly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>> error: connection to server was lost
> Look at the OS system log.
Really the most detail would be in postgres' own log. I'd only
expect the system log to contain relevant info if the problem
turns out to be an overeager OOM killer --- but if that's what's
happening, we should be able to diagnose from the postmaster's
log too (because it'd show up as the backend dying from SIGKILL).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2024-04-14 17:19:16 | Re: constant crashing |
| Previous Message | Adrian Klaver | 2024-04-14 17:05:21 | Re: constant crashing |