Message-ID: <gh-postgresql-interfaces-psqlodbc-6-c2102473770@github.com>
From: "apgrucza (@apgrucza)" <noreply+apgrucza@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Thu, 09 May 2024 11:20:22 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] PR #6: Use mimalloc to improve performance and reduce memory allocation lock contention
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-6@github.com>
References: <gh-postgresql-interfaces-psqlodbc-6@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: apgrucza
X-GitHub-Comment-Id: 2102473770
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 6
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/pull/6#issuecomment-2102473770
Content-Type: text/plain; charset=utf-8

I disabled the caching in my fork so that I could test your changes. The x86 installer does now install the libssl and libcrypto DLLs. However, the DLL versions are not consistent between x86 and x64.

- **x86**: libpq.dll (17.0.0.0), libssl-3.dll (3.3.0.0)
- **x64**: libpq.dll (16.0.2.0), libssl-3-x64.dll (3.0.13.0)

Is it possible to build the x64 driver the same way as the x86 driver so that we can have some consistency? And to get the PostgreSQL code from a stable release, from https://www.postgresql.org/ftp/source/?