Question
doc/configuration.md describes the only_utxo preset as loading only block, tx, tx_out and ma_tx_out. But the preset enables governance, so a sync with preset: only_utxo populates the governance tables. Which side is correct?
Observed
db-sync 13.7.2.1, preview, insert_options: { preset: only_utxo }:
drep_registration | 22992
voting_anchor | 16881
gov_action_proposal | 1496
voting_procedure | 4950
Source
onlyUTxOInsertOptions (Cardano/DbSync/Config/Types.hs) sets:
sioGovernance = GovernanceConfig True
Git history: this was GovernanceConfig False until commit fda0c89 ("Add offchain_vote_data config flag, default disabled for pools and votes"), which flipped it to True. That commit is about a different flag, and the flip has no CHANGELOG entry, no doc update, and no test asserting it, so it is not clear whether it was intentional.
Resolution
Either:
- Governance should be off for only_utxo: set
sioGovernance = GovernanceConfig False.
- Governance is intended to be on: update doc/configuration.md, which is wrong about more than governance (the preset also enables multi_asset, and the rewards/epoch flags), so the "only block, tx, tx_out, ma_tx_out" line needs a rewrite either way.
Question
doc/configuration.mddescribes the only_utxo preset as loading onlyblock,tx,tx_outandma_tx_out. But the preset enables governance, so a sync withpreset: only_utxopopulates the governance tables. Which side is correct?Observed
db-sync 13.7.2.1, preview,
insert_options: { preset: only_utxo }:Source
onlyUTxOInsertOptions(Cardano/DbSync/Config/Types.hs) sets:Git history: this was
GovernanceConfig Falseuntil commit fda0c89 ("Add offchain_vote_data config flag, default disabled for pools and votes"), which flipped it toTrue. That commit is about a different flag, and the flip has no CHANGELOG entry, no doc update, and no test asserting it, so it is not clear whether it was intentional.Resolution
Either:
sioGovernance = GovernanceConfig False.