postgresql-interfaces/psqlodbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: progmachine (@progmachine) <[email protected]>
To: postgresql-interfaces/psqlodbc <[email protected]>
Subject: Re: [postgresql-interfaces/psqlodbc] issue #8: Memory leaks detected in psqlodbc library
Date: Wed, 15 May 2024 15:20:52 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
I think it is easy to reproduce:
1. Create two statements within one connection.
2. With first statement execute select command, and get Columns info with `SQLDescribeCol` function.
3. With second statement execute `ALTER TABLE`/`DROP TABLE` sql command. This will call `CC_clear_col_info` to clear COL_INFO cache.
4. Check again column info with first statement, that should access cached COL_INFO object, that was deleted on step 3 because of your modification.
But without AddressSanitizer, it can work well, until freed memory used again before step 4.
view thread (31+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://postgresql-interfaces/psqlodbc
Cc: [email protected], [email protected]
Subject: Re: [postgresql-interfaces/psqlodbc] issue #8: Memory leaks detected in psqlodbc library
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox