Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
Дата
Msg-id 6A578237-999A-4CE5-9981-29FBA4C0EED9@yesql.se
обсуждение исходный текст
Ответ на Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]  (Kirk Wolak <wolakk@gmail.com>)
Ответы Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]  (Kirk Wolak <wolakk@gmail.com>)
Список pgsql-hackers
> On 19 Jan 2024, at 23:09, Kirk Wolak <wolakk@gmail.com> wrote:

>  From a FUTURE email, I noticed pg_jit_available() and it's set to f??

Right, then this installation does not contain the necessary library to JIT
compile the query.

> Okay, so does this require a special BUILD command?

Yes, it requires that you compile with --with-llvm.  If you don't have llvm in
the PATH you might need to set LLVM_CONFIG to point to your llvm-config binary.
With autotools that would be something like:

    ./configure <other params> --with-llvm LLVM_CONFIG=/path/to/llvm-config

--
Daniel Gustafsson




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan
Следующее
От: Jeff Davis
Дата:
Сообщение: Re: Change GUC hashtable to use simplehash?