Releases: mutable-org/mutable
Releases · mutable-org/mutable
v0.0.41
[V8] Disable lazy compilation iff adaptive execution is disabled.
v0.0.40: [Benchmark] Improve PostgreSQL connector.
- Do not `kill()` while handling `TimeoutExpired`. This should happen only in `finally` and after an attempt at graceful termination. - Properly dispose of connections by `del`-eting them.
v0.0.39
[Wasm] Adapt partition function in `quicksort()`.
v0.0.38
[Benchmark] Kill child processes on timeout
v0.0.37
[Doc] Add README.md documentation for `Spn`.
v0.0.36: [Benchmark] Explicitly flush after `tqdm.write()`.
Apparently, calls to `tqdm.write()` do *not* flush the output to the output stream (`sys.stdout`). We now do this manually after calls to `tqdm.write()`.
v0.0.35
[Benchmark] Fix wrong indent in hyper connector
v0.0.34
[UTest] Add tag [core][catalog][schema] for TEST_CASE("Table empty ac…
v0.0.33: [Benchmark] Fix PostgreSQL timeout and clean-up.
- The *process* of the query within the PostgreSQL server can reach a timeout. In that case, we kill the `psql` client. This, however, does not stop the *process* within the server. Consequently, clean-up after an experiment trying to run `DROP DATABASE` will trigger an error, as a table in the DB to drop is still in use. To properly *"kill"* the server *process* we install *in PostgreSQL* a timeout with `set statement_timeout`. This has the server kill *processes* that reach the specified timeout. - The clean-up after an experiment must `DROP DATABASE` the table with the benchmark input data. This was run incorrectly in one iteration of a loop right before the next iteration would attempt to that exact database, which would then have been dropped. We generally change the structure of the code to use *local* `psycopg2` connections and always close them properly in a `finally` section. Further, the `run_command()` no longer runs `clean_up()` itself.
v0.0.32
[WasmDSL] Remove constraint from `Variable`s default c'tor.