Message-ID: <gh-postgresql-interfaces-psqlodbc-6-c2100625539@github.com>
From: "apgrucza (@apgrucza)" <noreply+apgrucza@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Wed, 08 May 2024 13:49:54 +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: 2100625539
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-2100625539
Content-Type: text/plain; charset=utf-8

BTW the usage of `actions/cache` is causing certain steps to be skipped when they shouldn't be. For example, the "build postgresx86" step in [this run](https://github.com/postgresql-interfaces/psqlodbc/actions/runs/8992393964) was skipped even though the [commit that triggered it](https://github.com/postgresql-interfaces/psqlodbc/commit/03dec03835839a90948237af271317a54a0575a3) changed that step. Not sure what the best solution to this is, but one option is to include in the [cache key](https://github.com/actions/cache?tab=readme-ov-file#creating-a-cache-key) a hash of all files that affect the contents of `d:\postgresql86`, including `.github/workflows/main.yml` itself.