On Mon, Feb 14, 2022 at 7:31 AM Michael Paquier <michael@paquier.xyz> wrote:
On Fri, Feb 11, 2022 at 07:50:44AM -0800, Andres Freund wrote:
> I hit this as well. The problem is really caused by using a debug build of > postgres vs a production build of zlib. The use different C runtimes, with > different file descriptors. A lot of resources in the windows world are > unfortunately tied to the C runtime and that there can multiple C runtimes in > a single process.
It may be worth warning about that at build time, or just document the matter perhaps? I don't recall seeing any MSIs related to zlib that have compile with the debug options.
Building with a mix of debug and release components is not a good practice for issues like this, but is not something that MSVC forbids. If this is something we want to discard altogether, we can check at build time with 'dumpbin' to ensure that all dlls share the same vcruntime.dll.
