Re: BUG #18408: ERROR: could not load library

Поиск
Список
Период
Сортировка
От Sandeep Thakkar
Тема Re: BUG #18408: ERROR: could not load library
Дата
Msg-id CANFyU94sVqbL3kT9-w3=1Fv8nNHozJkjyyu5_8BFTiDO-jHN2Q@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #18408: ERROR: could not load library  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Hi,

One of the possibilities could be that the dependency for "C:/Program
Files/PostgreSQL/16/lib/plpython3.dll" is not resolved 


On Tue, Mar 26, 2024 at 7:53 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18408
Logged by:          Ben Watson
Email address:      ben.watson@maroonanalytics.com
PostgreSQL version: 16.2
Operating system:   Win11
Description:       

I have been trying to get PostgreSQL 16.2, compiled by Visual C++ build
1937, 64-bit running on a win11 machine. I am having a number of issues, but
one that looks very much like a bug

CREATE EXTENSION plpython3u;

Throws this error. ERROR: could not load library "C:/Program
Files/PostgreSQL/16/lib/plpython3.dll": The specified module could not be
found.

But the file clearly exists in that directory.

But the because it is a windows machine the path should really be
"C:\Program Files\PostgreSQL\16\lib\plpython3.dll". Looks like some unix
style file paths are in use.

Is this a bug? or just misleading output. In any case that command does not
work in my environment.

PS running the sql shell as admin or not admin makes no difference.



--
Sandeep Thakkar


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

Предыдущее
От: "1165125080"
Дата:
Сообщение: RE: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
Следующее
От: Subhrajit Mutsuddi
Дата:
Сообщение: Walsender getting klilled, ERROR: out of memory in server logs