Maksim Kaitmazian authored 5 months ago and Dmitry Ivanov committed 5 months ago

With these changes, a user can specify new default values for vdbe_max_steps
vtable_max_rows options in connection string.

For example, the following connection string sets both options to 42:
postgres://postgres:Passw0rd@localhost:5432?options=vtable_max_rows%3D42,vdbe_max_steps%3D42

Add alter system cluster_wal_max_size and cluster_wal_max_count parameters
which control the auto compaction of _raft_log system space based on
the size in bytes and number of tuples respectively.

Previously all DELETE operations were executed via space api. Primary keys were materialized and passed tuple by tuple to the `delete` function. Under Delete node we always put a Motion with policy Local to materialize tuples to delete.

This commit brings an optimization for the case of DELETE without WHERE condition. Such queries are translated into local SQL and don't require tuples materialization from target relation (from which we delete). We don't add a Motion node under Delete in such cases.

feat: add sbroad-cartridge Makefile task to run integration tests only by pattern (without group specification)