| From: | Francisco Olarte <folarte(at)peoplecall(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 09:55:13 |
| Message-ID: | CA+bJJbwfL3Jf+9vxHJv5j-4Nej01UHBJELB+5eH1rC0vXEaRrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Just a comment...
On Tue, 26 Mar 2024 at 03:23, PG Bug reporting form
<noreply(at)postgresql(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2024-03-26 10:07:20 | Re: BUG #18408: ERROR: could not load library |
| Previous Message | Wolfgang Walther | 2024-03-26 08:22:28 | Building with musl in CI and the build farm |