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

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: "Yeddula, Madhusudhan reddy [CONTINGENT WORKER]" <myeddula(at)informatica(dot)com>, "Mathias, Renci" <rmathias(at)informatica(dot)com>, "Sahu, Abhisek Kumar" <absahu(at)informatica(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "Sachan, Vishal" <vsachan(at)informatica(dot)com>
Cc: "Kumar, Gaurav" <gaurkumar(at)informatica(dot)com>, "Nayak, Deepak Vaikunta" <dnayak(at)informatica(dot)com>
Subject: Re: BUG #18569: Memory leak in Postgres Enterprise server
Date: 2024-09-21 00:28:21
Message-ID: b07d8420-f294-42a8-937d-365c5c4c6c41@vondra.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2024-09-21 05:56:22 Re: vacuumdb: permission denied for schema "pg_temp_7"
Previous Message Tomas Vondra 2024-09-21 00:23:12 Re: BUG #18569: Memory leak in Postgres Enterprise server