MIME-Version: 1.0
References: 
 <CA+FWGK4zEPLE94c83xbTFcZVEgGma5pJ+7tnxHpk4okuQ750Jg@mail.gmail.com>
In-Reply-To: 
 <CA+FWGK4zEPLE94c83xbTFcZVEgGma5pJ+7tnxHpk4okuQ750Jg@mail.gmail.com>
From: Muhammad Ikram <me.mikram@gmail.com>
Date: Wed, 16 Oct 2024 08:37:27 +0500
Message-ID: 
 <CAJQ7xG4BV_fbB06=OSRKFq0JaQ2GW0mK11J_yxuSSri15TzQ7Q@mail.gmail.com>
Subject: Re: work_mem memory usage statistics
To: Loles <lolesft@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000a6dc6306248fca0c"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJQ7xG4BV_fbB06%3DOSRKFq0JaQ2GW0mK11J_yxuSSri15TzQ7Q%40mail.gmail.com>
Precedence: bulk

--000000000000a6dc6306248fca0c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

- No built-in routine or extension is there to show aggregation of work_mem
for any query, as it is dynamically allocated.
- If work_mem requirement exceeds then it spills to disk, which can be
monitored through logs. Use log_temp_files and log_statement_stats to see
temp files, their size may give clues.
- pg_stat_statements and pg_stat_activity may also help in getting an idea
about which queries are taking more time and their consumption of shared
blocks etc.

Regards,
Ikram

On Tue, Oct 15, 2024 at 11:46=E2=80=AFPM Loles <lolesft@gmail.com> wrote:

> Hi team,
>
> Is there any statistics table or view in the PostgreSQL catalog,
> extension, or similar that collects and displays work_mem memory usage
> statistics? It would be interesting to know the use of the work_mem by
> user, application and/or database.
>
> Thanks in advance.
>
> Loles
>

--000000000000a6dc6306248fca0c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br>Hi,<div><br><div>- No built-in routine or extension is=
 there to show aggregation of work_mem for any query, as it is dynamically =
allocated.<br>- If work_mem requirement exceeds then it spills to disk, whi=
ch can be monitored through logs. Use log_temp_files and log_statement_stat=
s to see temp files, their size may give clues.<br>- pg_stat_statements and=
 pg_stat_activity may also help in getting an idea about which queries are =
taking more time and their consumption of shared blocks etc.<br><br>Regards=
,<br>Ikram<br></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Tue, Oct 15, 2024 at 11:46=E2=80=AFPM Loles &l=
t;<a href=3D"mailto:lolesft@gmail.com">lolesft@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv>Hi team,</div><div><br></div>Is there any statistics table or view in th=
e PostgreSQL catalog, extension, or similar that collects and displays work=
_mem memory usage statistics? It would be interesting to know the use of th=
e work_mem by user, application and/or database.<div><br></div><div>Thanks =
in advance.<br></div><div><br></div><div>Loles</div></div>
</blockquote></div>

--000000000000a6dc6306248fca0c--