Re: BUG #18569: Memory leak in Postgres Enterprise server

On 9/21/24 02:23, Tomas Vondra wrote:
> 
> ...
>
> Application log is not very useful for investigating this, because it
> only says this:
> 
>     server closed the connection unexpectedly
> 
>     This probably means the server terminated abnormally
> 
>     before or while processing the request.
> 
> So, the database connection went away, but we're none the wiser why. We
> don't even know if it was the query reported in the application log
> causing the issue, it might have been some other process causing the
> crash, and this query is just a victim.
> 
> You need to inspect the database log, which might tell you more - either
> which backend actually crashed / why, possibly some additional info.
> Also look at dmesg, which should have info about OOM killer, if that's
> what killed one of the processes.
> 

BTW I noticed there's a separate "memory leak" report from you. Is that
related to the same database/instance?


-- 
Tomas Vondra