Date: Tue, 17 Sep 2024 21:04:52 +0200
From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: Thomas Ziegler <thomas.ziegler@holmsecurity.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: Failing to allocate memory when I think it shouldn't
Message-ID: <ZunS1AP1XiKXtLzw@elch.exwg.net>
References: <PAWPR07MB1009548159C0046E01170C6E6ED652@PAWPR07MB10095.eurprd07.prod.outlook.com>
 <ZuXuDdq32fuzI8pp@elch.exwg.net>
 <f8abb93a-5b03-4c0e-a69f-1f3cdfd4c4d4@holmsecurity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <f8abb93a-5b03-4c0e-a69f-1f3cdfd4c4d4@holmsecurity.com>
User-Agent: Mutt/2.2.13 (2024-03-09)
Archived-At: <https://www.postgresql.org/message-id/ZunS1AP1XiKXtLzw%40elch.exwg.net>
Precedence: bulk

Hi,

## Thomas Ziegler (thomas.ziegler@holmsecurity.com):

> Except for pgAudit, I don't have any extensions, so it is probably the
> JIT. I had no idea there was a JIT, even it should have been obvious.
> Thanks for pointing this out!

There is - it even has it's own chapter in the documentation:
https://www.postgresql.org/docs/current/jit.html
Most importantly, you can disable JIT per session ("SET jit=off")
or globally in the configuration file (jit=off, reload is
sufficient) or with any of the other usual configuration mechanisms.
If that fixes your problem, congratulations (and the problem is
somewhere down between bytecode generation and what and how llvm
(in its particular version) generates from that).

> Is the memory the JIT takes limited by 'work_mem' or will it just take
> as much memory as it needs?

The latter.

Regards,
Christoph

-- 
Spare Space