Horton
Menu

Re: doc: pgevent.dll location

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: "Ryohei Takahashi (Fujitsu)" <r.takahashi_2@fujitsu.com>, Dave Page <dpage@pgadmin.org>, Gurjeet Singh <gurjeet@singh.im>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2024-11-12T21:11:44Z
Lists: 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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. meson: Build pgevent as shared_module rather than shared_library