pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18408: ERROR: could not load library
4+ messages / 4 participants
[nested] [flat]
* BUG #18408: ERROR: could not load library
@ 2024-03-26 00:04 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 2 replies; 4+ messages in thread
From: PG Bug reporting form @ 2024-03-26 00:04 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: ben.watson@maroonanalytics.com
The following bug has been logged on the website:
Bug reference: 18408
Logged by: Ben Watson
Email address: ben.watson@maroonanalytics.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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #18408: ERROR: could not load library
@ 2024-03-26 03:55 Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
parent: PG Bug reporting form <noreply@postgresql.org>
1 sibling, 0 replies; 4+ messages in thread
From: Sandeep Thakkar @ 2024-03-26 03:55 UTC (permalink / raw)
To: ben.watson@maroonanalytics.com; pgsql-bugs@lists.postgresql.org
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@postgresql.org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18408
> Logged by: Ben Watson
> Email address: ben.watson@maroonanalytics.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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #18408: ERROR: could not load library
@ 2024-03-26 09:55 Francisco Olarte <folarte@peoplecall.com>
parent: PG Bug reporting form <noreply@postgresql.org>
1 sibling, 1 reply; 4+ messages in thread
From: Francisco Olarte @ 2024-03-26 09:55 UTC (permalink / raw)
To: ben.watson@maroonanalytics.com; pgsql-bugs@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #18408: ERROR: could not load library
@ 2024-03-26 10:07 Andrew Dunstan <andrew@dunslane.net>
parent: Francisco Olarte <folarte@peoplecall.com>
0 siblings, 0 replies; 4+ messages in thread
From: Andrew Dunstan @ 2024-03-26 10:07 UTC (permalink / raw)
To: Francisco Olarte <folarte@peoplecall.com>; +Cc: ben.watson@maroonanalytics.com; pgsql-bugs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2024-03-26 10:07 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-03-26 00:04 BUG #18408: ERROR: could not load library PG Bug reporting form <noreply@postgresql.org>
2024-03-26 03:55 ` Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
2024-03-26 09:55 ` Francisco Olarte <folarte@peoplecall.com>
2024-03-26 10:07 ` Andrew Dunstan <andrew@dunslane.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox