Request a Demo
Home   >   mailing lists

Re: BUG #19095: Test if function exit() is used fail when linked static - Mailing list pgsql-bugs

From VASUKI M
Subject Re: BUG #19095: Test if function exit() is used fail when linked static
Date
Msg-id CACTYHzgb=1UXNoW08AjBBUB10dZPoAg4pptFm3K63V5xs=j=Jw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19095: Test if function exit() is used fail when linked static  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #19095: Test if function exit() is used fail when linked static
List pgsql-bugs
Tree view

Thanks Michael and Peter for the detailed reviews and for taking the time to refine and commit the updated version.

Thanks for pointing out that pgperltidy may behave differently across environments.

On Tue, 9 Dec 2025 at 11:56, Michael Paquier <michael@paquier.xyz> wrote:

The attached takes care of the issue here.  Adding that to pgxs_bins
may look adapted at first glance, but I don't quite see the point in
exposing this information to PGXS, so pgxs_empty is a better fit?

Thanks for the clarification.Given that PGXS extensions don't appear to require NM ,IMO adding it to pgxs_empty makes sense to me.It resolves the Meson warning without exposing unnecessary variables to PGXS users.

Regards,
Vasuki M

pgsql-bugs by date:

Previous
From: "Haowu Ge"
Date:
Subject: Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Next
From: PG Bug reporting form
Date:
Subject: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7