| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: _CRT_glob stuff |
| Date: | 2025-09-22 15:46:22 |
| Message-ID: | CAOYmi+=qr-iOx36xCYE1U539-fhh7o1cidZENFarFzXFWxA7uw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 19, 2025 at 12:37 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> As to how it works, I'm not sure, but I suppose the linker somehow
> arranges the initializations in the right order.
Okay. I was a bit concerned that, if libpq pulled in this symbol via
pgcommon, it might accidentally affect the client executable... but I
guess our exports files are saving us there, and in any case the
executable's symbol (if defined) should win anyway. Carry on :)
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Константин Книжник | 2025-09-22 16:44:18 | Re: Orphan page in _bt_split |
| Previous Message | Fujii Masao | 2025-09-22 15:44:23 | Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ? |