Re: PostgreSQL Out of Memory

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: liam saffioti <liam(dot)saffiotti(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL Out of Memory
Date: 2022-09-07 00:41:48
Message-ID: CAMkU=1xRyqHWpdkpRqU3-+4LXS42zVGP1xBguMaijeLLuV=2JQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, Sep 5, 2022 at 7:55 AM liam saffioti <liam(dot)saffiotti(at)gmail(dot)com>
wrote:

> Hi Teams,
>
> I have PG 14.5 on RHEL 8.4. I see many errors. Do you have any idea about
> this problem?
>
> TopMemoryContext: 1194808 total in 12 blocks; 3968 free (3 chunks);
> 1190840 used
> TopTransactionContext: 592728 total in 9 blocks; 30328 free (4 chunks);
> 562400 used
> ExecutorState: 551680 total in 8 blocks; 147192 free (31 chunks);
> 404488 used
> BTree array context: 4096 total in 3 blocks; 3488 free (9 chunks);
> 608 used
> TupleSort main: 3153976 total in 2 blocks; 6728 free (7 chunks);
> 3147248 used
> TupleSort sort: 8192 total in 1 blocks; 7928 free (0 chunks); 264
> used
> Caller tuples: 16777216 total in 12 blocks; 624 free (13
> chunks); 16776592 used
>

The problem context is probably hiding inside the ellipsis.

What is the single largest line (according to the first numeric field) from
this report?

Cheers,

Jeff

>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Victor Sudakov 2022-09-09 04:56:24 WAL storage when archive_command=''
Previous Message Mladen Gogala 2022-09-05 15:25:55 Re: PostgreSQL Out of Memory