Message-ID: <gh-postgresql-interfaces-psqlodbc-189-c4590919620@github.com>
From: "cipriani-ivan (@cipriani-ivan)" <noreply+cipriani-ivan@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Mon, 01 Jun 2026 08:39:10 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #189: Possible double-free / heap corruption in psqlODBC during SQLDisconnect cleanup
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-189@github.com>
References: <gh-postgresql-interfaces-psqlodbc-189@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: cipriani-ivan
X-GitHub-Comment-Id: 4590919620
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 189
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/189#issuecomment-4590919620
Content-Type: text/plain; charset=utf-8


Hi @davecramer,
Thank you again for providing the proposed fix in #190.
I’ve been able to build and test the driver from the branch. Unfortunately, we are still able to reproduce a crash during the same teardown scenario. The behavior has changed slightly, though:

The process still terminates during cleanup after a failed connection
Instead of the previous heap corruption signature, we now consistently see:
FATAL: terminating connection due to administrator command


The crash still occurs in the same general flow (connection failure → immediate disposal → cleanup)

In addition, we are observing similar instability in a few other failure scenarios, particularly in situations where a connection is closed and a new one is created shortly after.
So while the symptom has changed, it seems the underlying issue is not fully resolved yet.

Thanks again for your work on this.
Best regards,