GitLab

fix mocks linter errors

See merge request !72

update doc: more descriptive synchronization state machine diagram

See merge request !71

issue #31: index are recreated after reindex

See merge request !59

It turned out that indexes to much slow down P2P sync

Update README.md

See merge request !69

when starting hive by replay and then going to live sync

See merge request !67

Update README.md

See merge request !68

when starting hived by replay and then going to live sync (without p2p sync stage)
for hive_fork_managed all blocks send during replay are irreversible
for core of hive during replay irreversible is arout 20 blocks behind head

update doc: pg_dump and psql extensions

See merge request !66

'START' state is the start state of synchronization.
Inside this state decision is made in which state synchronization
muste go next. During this state synchronization is not synchronizing
blocks, only wait for event which claryfy what is the most optimal next
state. 'START' state solves the problem with breaking LIVE
synchronization with CTRL+C: previously at the begining synchronization
was started in P2P state, what fore to disable foreign key, and in
consequence the FK have to be restored in the next state what takes a
lot of time. Now, during leaving the 'START' state decision is made if
is better go to LIVE or P2P/REINDEX. Decision is made on expected
number of blocks to sync to reach the network HEAD BLOCK. A new
parameter 'psql-livesync-threshold' was added to sql_serializer: if
number of expected blocks is less or equal than the value of the threshold then
synchronization will move to live sync, otheriwse to it will move to
P2P/REINDEX.

New class to manipulation of indexes and contraints added: indexes_controller
indexation_state enable/disable indexes and foreign key depends on its state
When the node is broken with CTRL+C then nothing happen with the indexes
P2P sync works with enabled indexes and disabled FK
REINDEX sync works with disabled indexes and disabled FK
LIVE sync works with enabled indexes and enabled FK

always blocks operation handlers regardles of synchronization state

See merge request !58

Update README.md

See merge request !65

Update README.md

See merge request !64

Update src/sql_serializer/README.md

See merge request !63

Update src/hive_fork_manager/Readme.md

See merge request !62

Update README.md

See merge request !61

documentation update

See merge request !57

- one common installtion itruction for whole HAF
- sql_serializer parameter description
- cmake targets types
- sql_serialzier: dumping blocks to the datatabase

add dirty flag to make node to db reconnection faster

See merge request !56

The table hive.irreversible_data was extended to column dirty (boolean).
When dirty is TRUE it means that irreversible data are in inconsistent state.
When the HAF will crash during sync (replay or p2p sync) then data are
inconsistant: some dumping data thread finish their jobs and some do not.
When node after crash will start, then it checks the dirty flag, if flag
is set, then inconsistent data have to be removed but it may last very long
time, because during replay there are no indexes to make inserting new rows faster.
During restarting the HAF after the crash an error is returned with informations about datat inconistency.
To succesfuly restart the node the switch `--psql-force-open-inconsistent` must be used.

Defined additional index covering hive.accounts::block_num column

See merge request !54

Defined additional index covering hive.accounts::block_num column to speedup `hive.remove_inconsistend_irreversible_data()` call.

remove uneeded join account_operations with operations during hive.connect

See merge request !53

Implementation of `get_impacted_balances`

See merge request !22