| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Avi Weinberg <AviW(at)gilat(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres Out Of Memory Crash |
| Date: | 2023-11-02 10:46:39 |
| Message-ID: | e089bb800a72c70fecd03b1d119c8d6fc567c717.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2023-11-02 at 09:12 +0000, Avi Weinberg wrote:
> I'm using Patroni Postgres installation and noticed that twice already postgres
> crashed due to out of memory. I'm using logical replication with around 30-40
> active subscribers on this machine. The machine has 128GB but only 32GB is allocated
> to Postgres. How can I know what is actually causing the out of memory issue?
> Is it caused by not optimal postgres configuration or something else?
You should look into the PostgreSQL log. That should show a message like
LOG: server process (PID 16024) was terminated by signal 9: Killed
DETAIL: Failed process was running: SELECT ...
It is not certain, but often that statement is the one that used up
all that memory. At least it is a starting point for your investigation.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kar, Swapnil (TR Technology) | 2023-11-03 06:26:21 | Postgres limitation in user management |
| Previous Message | Paul Förster | 2023-11-02 09:46:19 | Re: pg_checksums? |