Re: pg_receivewal.exe unhandled exception in zlib1.dll

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_receivewal.exe unhandled exception in zlib1.dll
Date: 2022-02-15 10:21:42
Message-ID: CAC+AXB0bTiuiEFMVp-1s5XM8e1Mabp1VeGYuTMVvZvB_T5S+bA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 14, 2022 at 7:31 AM Michael Paquier <michael(at)paquier(dot)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.

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-02-15 10:35:15 Re: Skipping logical replication transactions on subscriber side
Previous Message Peter Eisentraut 2022-02-15 10:16:12 Re: fixing bookindex.html bloat