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

From: Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>
To: ben(dot)watson(at)maroonanalytics(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18408: ERROR: could not load library
Date: 2024-03-26 03:55:44
Message-ID: CANFyU94sVqbL3kT9-w3=1Fv8nNHozJkjyyu5_8BFTiDO-jHN2Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18408
> Logged by: Ben Watson
> Email address: ben(dot)watson(at)maroonanalytics(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Subhrajit Mutsuddi 2024-03-26 04:24:25 Walsender getting klilled, ERROR: out of memory in server logs
Previous Message 1165125080 2024-03-26 02:36:31 RE: BUG #18386: Slow connection access after 'vacuum full pg_attribute'