Message-ID: <gh-postgresql-interfaces-psqlodbc-47-c2380250454@github.com>
From: "siga0984 (@siga0984)" <noreply+siga0984@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Fri, 27 Sep 2024 22:54:55 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #47: Memory Corruption using version 16.00.0005
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-47@github.com>
References: <gh-postgresql-interfaces-psqlodbc-47@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: siga0984
X-GitHub-Comment-Id: 2380250454
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 47
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/47#issuecomment-2380250454
Content-Type: text/plain; charset=utf-8

@progmachine @davecramer 

Maybe I found where is the catch ... After prepare two statements with the same SQL expression, leave both opened , DROP any table, and close the statements, I got the double delete error !!! 

Seems like it's related to CC_clear_col_info() , called on DROP TABLE 🎸