Re: Question regarding dynamic_library_path

Oh, sorry. This HP-UX 11.x. But you can get the same using shl_load (HP-UX
10.x) and pass the flag DYNAMIC_PATH provided the executable is linked with
+s. So it's still no showstopper.

If you do find that it is impossible on some older OS (HP-UX 11 arrived 4
years ago), then why not just disable this feature on that particular
version of the OS and make a note for the user that in order to get it, it's
time to upgrade?

IMO it's not a good policy to prevent new good features just to keep
customers sticking to old stuff from feeling bad not getting them. You need
to assure backward compatibility to keep everyone happy.

Kind regards,

Thomas Hallgren

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas Hallgren" <thhal(at)mailblocks(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Wednesday, June 09, 2004 7:24 AM
Subject: Re: [HACKERS] Question regarding dynamic_library_path

> "Thomas Hallgren" <thhal(at)mailblocks(dot)com> writes:
> >> ... Furthermore, AFAICT shl_load()
> >> requires an exact path spec for the initial shared library; it won't
> >> do a path search for that, only for dependencies.)
> >>
> > Here's an excerpt from the HPUX manual pages on dlopen(3C).
>
> HPUX which? There is no dlopen() in HPUX 10.20, which is what
> I'm running here; nor do we use dlopen() in any HPUX version
> given the current state of port/dynloader/hpux.c.
>
> regards, tom lane
>