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

From Francisco Olarte
Subject Re: BUG #18408: ERROR: could not load library
Date
Msg-id CA+bJJbwfL3Jf+9vxHJv5j-4Nej01UHBJELB+5eH1rC0vXEaRrQ@mail.gmail.com
Whole thread Raw
In response to BUG #18408: ERROR: could not load library  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18408: ERROR: could not load library  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-bugs
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.

Francisco Olarte.



pgsql-bugs by date:

Previous
From: walther@technowledgy.de
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Next
From: Andrew Dunstan
Date:
Subject: Re: BUG #18408: ERROR: could not load library