Message-ID: <gh-postgresql-interfaces-psqlodbc-113-c2840493530@github.com>
From: "harukat (@harukat)" <noreply+harukat@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Wed, 30 Apr 2025 00:04:31 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] PR #113: SQLFreeStmt(stmt,SQL_DROP) now returns an error when it's conn has been disconnected.
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-113@github.com>
References: <gh-postgresql-interfaces-psqlodbc-113@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: harukat
X-GitHub-Comment-Id: 2840493530
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 113
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/pull/113#issuecomment-2840493530
Content-Type: text/plain; charset=utf-8

> @harukat has this fixed the issue for you ?

Yes.
At least in the crash reproduction steps that I am aware of, it no longer reproduces after applying this fix.

However, we have subsequently received reports of psqlodbc crashing under similar circumstances after applying this fix. I have not yet been able to analyze this issue and have not established a procedure to reproduce it.