Re: pgbench error: (setshell) of script 0; execution of meta-command failed
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Andy Fan <zhihuifan1213@163.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-01-14T20:49:27Z
Lists: pgsql-hackers
On Tue, Jan 14, 2025 at 02:52:29PM -0500, Tom Lane wrote: > After more thought I've realized that the asymmetrical detection > here isn't all that bad, because the outcomes are different. > If we fail to catch old-headers-and-new-library, the result will > either be a link failure or (if the extension uses libpq) silently > linking to libpq's pqsignal, which was likely not what was intended. > If we fail to catch the other case, the result is always a link > failure, and that will happen at build time not in the field. Assuming libpgport is only used as a static library, I think that makes sense. My web searches indicate that it is possible to do things like convert a static library to a dynamic one, but perhaps that's far enough beyond the realm of things we care about. > So now I'm inclined to include the ABI-compatible wrapper, which > will ensure that extensions continue to link to libpgport's pqsignal. Fine by me. -- nathan
Commits
-
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c.
- cfd7aadebea1 13.19 landed
- b935691b8b2f 16.7 landed
- a3b709cf73e0 15.11 landed
- a0dfeae0dc9a 17.3 landed
- 9a45a89c38f3 18.0 landed
- 02e69313ad0c 14.16 landed
-
Suppress macOS warnings about duplicate libraries in link commands.
- 06843df4abc5 17.0 cited