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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Francisco Olarte <folarte(at)peoplecall(dot)com>
Cc: 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 10:07:20
Message-ID: CAD5tBc+ptyd+282kAAkqBecAqNcit1QQ25hRwyMPW5iXAkrSuA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 26, 2024 at 5:55 AM Francisco Olarte <folarte(at)peoplecall(dot)com>
wrote:

> 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.
>
>
>

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2024-03-26 10:42:42 Re: Walsender getting klilled, ERROR: out of memory in server logs
Previous Message Francisco Olarte 2024-03-26 09:55:13 Re: BUG #18408: ERROR: could not load library