Skip to content
Snippets Groups Projects
Select Git revision
  • kusancho/march25/test_install_plugin_refactor
  • max/type-system-rs
  • vbabayan/1430-minimal-metrics-enchancement
  • master default protected
  • ekhamitov/1360-distributed-globally-v2
  • dkr/enlarge-port-range
  • kusancho/march25/apply_parameter_refactor
  • kusancho/february25/waiting_for_ddl_commit
  • artshmelev/message-about-ldap-connection-problem
  • 25.1 protected
  • kbezuglyi/alter_table_explicit_multiargument
  • vshunkov/cache_fallback
  • vildanov/1099-fix-not-in
  • gmoshkin/migration-lock-already-acquired
  • kbezuglyi/governor_upgrade_script
  • vshunkov/luarocks protected
  • vildanov/1374-group-by-aliases
  • vbabayan/1219-cas-proposal-dropped-errors-should-be-automatically-retried
  • dixitix/ignore-alien-messages
  • astrochuk/remove-dag
  • 25.1.1 protected
  • 25.2.0 protected
  • 1.7.4 protected
  • 24.6.1 protected
  • 24.7.0 protected
  • 24.6.1-rc1 protected
  • 24.3.4 protected
  • 24.5.1 protected
  • 24.6.0 protected
  • b-uroboros-supply-v1 protected
  • 24.3.3 protected
  • 24.4.1 protected
  • 24.5.0 protected
  • 24.3.2 protected
  • 24.2.4 protected
  • 24.2.3 protected
  • 24.4.0 protected
  • 24.3.1 protected
  • 24.2.2 protected
  • 24.2.1 protected
40 results
Compare
Georgy Moshkin's avatar
refactor: assert index is <= applied in compact_log instead of truncating
Georgy Moshkin authored 
We used to automatically truncate the index in compact_log if the caller
requested to compact too many entries. This made it so that the
requirement of not compacting any un-applied entries was implicit in our
code base, which is not good as it allows for some bugs to creep in
(like the one we fix a couple commits ago).

Now this is changed and instead of silently adjusting the index of last
compacted entry, we just assert that it's no greater than the applied
index. As a consequence there's a minor improvement in do_raft_log_auto_compaction
function.
0957624d
History
Georgy Moshkin's avatar 0957624d
History
Name Last commit Last update
.cargo
.gitlab/merge_request_templates
benchmark/pgbench
build-rs-helpers
certification_patches
debian
doc
docker-build-base
docker
gostech/gostech-audit-log
pico_proc_macro
picodata-plugin-proc-macro
picodata-plugin
rpm
sbroad
src
tarantool-build
test
tools
webui
http @ 77d70d35
tarantool @ 54bb4c3f
tarantool-sys @ fbd76a19
vshard @ 0687e96f
.dockerignore
.flake8
.gitattributes
.gitignore
.gitlab-ci.yml
.gitleaks.toml
.gitmodules
.justfile
.luacheckrc
.tool-versions
AUTHORS
CHANGELOG.md
CONTRIBUTING.md
Cargo.lock
Cargo.toml
LICENSE
Makefile
README.md
build.rs
exports_picodata
poetry.lock
pyproject.toml
pytest.ini
README.md

Picodata – Professional Data Management System for High Loads

This repository contains the source code of Picodata, an in-memory database with plugins in Rust.

What is Picodata

Picodata is a software for building professional data management systems. It provides an in-memory database together with a development platform and a runtime for custom plugins written in Rust. Learn more about our software at the picodata.io web site.

Getting Picodata

We provide pre-built Picodata packages for select Linux distributions including CentOS and Ubuntu. Head over to picodata.io/download to see what is available.

Running Picodata

Running a Picodata instance only takes one simple command:

picodata run

Getting a basic distributed cluster made of two instances running on different hosts involves two commands, like this:

picodata run --listen 192.168.0.1:3301
picodata run --listen 192.168.0.2:3301 --peer 192.168.0.1:3301

You can find out more about getting started procedures and first steps by heading to docs.picodata.io.

Building Picodata from source

Please refer to the CONTRIBUTING.md document for more detailed prerequisites, compilation instructions as well as steps required to run integration tests.