Re: pgsql: Default to hidden visibility for extension libraries where possi
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-committers@lists.postgresql.org
Date: 2022-07-18T02:34:42Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > I don't know how the configure exec bit got removed, shell history doesn't > show anything odd in that regard. I do see a mistake in locally merging the > symbol-visibility branch (leading to a crucial commit being missed). I do see > in shell history that I ran check-world without a failure just before pushing, > which should have shown the failure, but didn't. check-world would not have re-run configure even if it was out of date (only config.status), so that part of it's not so surprising. > Definitely a brown paper bag moment. We've all been there :-) regards, tom lane
Commits
-
Add PGDLLEXPORTS to some plpgsql function declarations
- 1caf915ff31e 16.0 landed
-
Default to hidden visibility for extension libraries where possible
- 089480c07705 16.0 cited
-
Expose a few more PL/pgSQL functions to debugger plugins.
- 53ef6c40f1e7 15.0 cited