Re: BUG #18408: ERROR: could not load library - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: BUG #18408: ERROR: could not load library
Date
Msg-id CAD5tBc+ptyd+282kAAkqBecAqNcit1QQ25hRwyMPW5iXAkrSuA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18408: ERROR: could not load library  (Francisco Olarte <folarte@peoplecall.com>)
List pgsql-bugs


On Tue, Mar 26, 2024 at 5:55 AM Francisco Olarte <folarte@peoplecall.com> wrote:
Just a comment...

On Tue, 26 Mar 2024 at 03:23, PG Bug reporting form
<noreply@postgresql.org> wrote:
> 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.

IIRC MSDOS has supported both slashes ( forward and backwards, / and \
) since 2.0, the first version with directories support.

Also, IIRC, they just added \ because of CP/M. CPM used /, not - for
options, MSDOS 1 copied it and in MSDOS 2 you needed a way to express
a path which would not be confused with an option.

So, better use /, case correct paths with are valid in both.




Yes, with very few exceptions forward slash paths work just fine on Windows.

The buildfarm animal drongo builds release 16 with python just fine. See <https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-03-25%2023%3A16%3A56>

cheers

andrew

pgsql-bugs by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: BUG #18408: ERROR: could not load library
Next
From: Laurenz Albe
Date:
Subject: Re: Walsender getting klilled, ERROR: out of memory in server logs