rusqlite ignoring sqlite3_hard_heap_limit64 (and soft limit), and sqlite3_memory_used always returns 0 about rusqlite HOT 11 CLOSED

Also noticing:

unsafe {
        sqlite3_soft_heap_limit64(1024);
        let soft_limit = sqlite3_soft_heap_limit64(-1);
        sqlite3_hard_heap_limit64(1024);
        let hard_limit = sqlite3_hard_heap_limit64(-1);
        println!("Soft limit: {} hard limit: {}", soft_limit, hard_limit);
    }

Soft limit: 1024 hard limit: 0

from rusqlite.

Are you sure that it is related to rusqlite ?
What happens if you use only C or any other language bindings ?

from rusqlite.

conn.pragma_update(
        Some(rusqlite::DatabaseName::Main),
        "hard_heap_limit",
        rusqlite::types::Value::Integer(1024),
    )?;
    conn.pragma_query(Some(rusqlite::DatabaseName::Main),
    "hard_heap_limit", |row | -> Result<()> {
        println!("hard heap limit pragma: {:?}", row);
        Ok(())
    }).unwrap();

also returns

hard heap limit pragma: {Ok("hard_heap_limit"): (Integer, 0)}

from rusqlite.

@gwenn I've just checked the SQLite cli on macOS:

 dangoodman: ~/code/learningRust/sqlite-test git:(main) ✗ sqlite3                                                                                          9:35AM
SQLite version 3.43.2 2023-10-10 13:08:14
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> PRAGMA hard_heap_limit;
0
sqlite> PRAGMA hard_heap_limit = 1024;
0
sqlite> PRAGMA hard_heap_limit;
0
sqlite> PRAGMA hard_heap_limit=1024;
0
sqlite> PRAGMA hard_heap_limit;
0
sqlite>

I assume this is compiled with the defaults which should allow it to be enabled as well

Seeing similar behavior with soft heap limits as the code:

sqlite> PRAGMA soft_heap_limit;
0
sqlite> PRAGMA soft_heap_limit=1024;
1024
sqlite> PRAGMA soft_heap_limit;
1024

from rusqlite.

Curious that it can't see it's own memory usage though as well no? All the checks and build flags indicate that this should be available. I'm not familiar with how to quickly test in another language that has such low level bindings to SQLite.

from rusqlite.

In case you don't know, you can ask for help here:
https://sqlite.org/forum/forum
but mainly for "official" projects or "general" questions related to SQLite.

from rusqlite.

Thanks, I wasn’t sure how much this might have been related to the build flags or any other config that might have been crate specific

from rusqlite.

You can use bundled feature temporarily if you are not sure of the flags used by your system library.

rusqlite = {version = "0.31.0", features = ["hooks", "bundled"]}

from rusqlite.

Will this use the flags from the crate build.rs?

from rusqlite.

Yes, these ones:

from rusqlite.

@gwenn thanks for the help, testing with a GH codespace using the provided sqlite I got:

config mem status enabled
Memory tracking is enabled. Current memory usage: 16168 bytes, Highwater mark: 16184 bytes
PRAGMA soft_heap_limit set to 1024
soft_heap_limit pragma: {Ok("soft_heap_limit"): (Integer, 1024)}
PRAGMA hard_heap_limit set to 1024
Error: SqliteFailure(Error { code: OutOfMemory, extended_code: 7 }, Some("out of memory"))

I assume bundling would also perform the same.

It seems the issue was my local version of sqlite on macOS!

from rusqlite.