Re: doc: pgevent.dll location - Mailing list pgsql-hackers

From Robert Haas
Subject Re: doc: pgevent.dll location
Date
Msg-id CA+TgmoaCFjcUmRu-GMV3E1G3wZLDm8O+-4XYdW8Zx_P2Z4+qqQ@mail.gmail.com
Whole thread Raw
In response to Re: doc: pgevent.dll location  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: doc: pgevent.dll location
List pgsql-hackers
On Tue, Nov 12, 2024 at 3:06 PM Peter Eisentraut <peter@eisentraut.org> wrote:
> On 12.11.24 18:27, Robert Haas wrote:
> > On Tue, Nov 12, 2024 at 11:52 AM Peter Eisentraut <peter@eisentraut.org> wrote:
> >> So the most straightforward way to "make it work like it used to" would
> >> be to change src/bin/pgevent/meson.build to use shared_module() instead
> >> of shared_library().
> >>
> >> Based on the explanation in the documentation, this file is really more
> >> of a plugin and less a shared library, so I think that approach would be
> >> more correct than not.
> >
> > I don't understand what the difference is between a shared module and
> > a shared library, so I find it odd that meson treats them differently.
>
> In this context, a shared module is something like plpgsql or hstore
> that you dlopen, and a shared library is something like libpq or libecpg
> that you -l at build time.

That's interesting, but I would have thought both of those would go in
libdir (or a subdirectory) not bindir.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Improve error messages for database object stats manipulation functions during recovery
Next
From: Heikki Linnakangas
Date:
Subject: Re: Statistics Import and Export