Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [ NOT Fixed ] - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [ NOT Fixed ]
Date
Msg-id CA+hUKGK_e6eUMqeR43cLmq8xXxh0dgnis3sEMi=NFmnLopp9ew@mail.gmail.com
Whole thread Raw
In response to Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [ NOT Fixed ]  (Kirk Wolak <wolakk@gmail.com>)
Responses Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [ NOT Fixed ]
List pgsql-hackers
On Thu, Jan 25, 2024 at 8:51 AM Kirk Wolak <wolakk@gmail.com> wrote:
>     getrusage(RUSAGE_SELF, &usage);
>     memory_usage_bytes = usage.ru_maxrss * 1024;

FWIW log_statement_stats = on shows that in the logs.  See ShowUsage()
in postgres.c.



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: UUID v7
Next
From: Sergey Prokhorenko
Date:
Subject: Re: UUID v7