Bogdan Kanivets d30a4fbf0c mvcc/backend: restore original bolt db options after defrag ...

Problem: Defrag was implemented before custom bolt options were added.
Currently defrag doesn't restore backend options.
For example BackendFreelistType will be unset after defrag.

Solution: save bolt db options and use them in defrag.

2022-02-17 15:33:05 -08:00

..

backend_bench_test.go

*: revert "internal/mvcc" change

2018-02-26 17:11:40 -08:00

backend_test.go

mvcc/backend: restore original bolt db options after defrag

2022-02-17 15:33:05 -08:00

backend.go

mvcc/backend: restore original bolt db options after defrag

2022-02-17 15:33:05 -08:00

batch_tx_test.go

mvcc/backend: use "go.etcd.io/bbolt"

2018-08-29 12:31:04 -07:00

batch_tx.go

mvcc: address comments

2019-06-13 18:05:50 -07:00

config_default.go

mvcc/backend: use "go.etcd.io/bbolt"

2018-08-29 12:31:04 -07:00

config_linux.go

mvcc/backend: use "go.etcd.io/bbolt"

2018-08-29 12:31:04 -07:00

config_windows.go

mvcc/backend: use "go.etcd.io/bbolt"

2018-08-29 12:31:04 -07:00

doc.go

*: revert "internal/mvcc" change

2018-02-26 17:11:40 -08:00

metrics.go

storage/backend: Add a gauge to indicate if defrag is active (backport from 3.6)

2021-10-06 11:04:47 -07:00

read_tx.go

mvcc: address comments

2019-06-13 18:05:50 -07:00

tx_buffer.go

mvcc: fully concurrent read

2019-05-08 19:11:23 -07:00