From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adrian Klaver <adrian.klaver@aklaver.com>
cc: jack <jack4pg@a7q.com>,
        "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: constant crashing
In-reply-to: <d833a2f4-9734-442f-907a-c32ee5fbd11f@aklaver.com>
References: <HgsD3gOH-K3PK0n7PogBu3X1goIJ3_kN04shv7womj--6jQcAggYWdAOqYOmq1VVlVPf6TiHvxpZCvwmFawmHMEjciHsLErgsjaLruEspg0=@a7q.com> <d833a2f4-9734-442f-907a-c32ee5fbd11f@aklaver.com>
Comments: In-reply-to Adrian Klaver <adrian.klaver@aklaver.com>
	message dated "Sun, 14 Apr 2024 10:05:21 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <512138.1713114818.1@sss.pgh.pa.us>
Date: Sun, 14 Apr 2024 13:13:38 -0400
Message-ID: <512139.1713114818@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/512139.1713114818%40sss.pgh.pa.us>
Precedence: bulk

Adrian Klaver <adrian.klaver@aklaver.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