1

Interested to understand why db sync snap shot does not include new consumed_tx_out column. Just upgraded to v3.1.1.3 using manual method (not docker) and restored most recent db snapshot from 4 days ago with the hope that these "fix" items would already be included. Why is this not the case? Also, what are the controls (non docker) for telling db sync "when to run" or "when not to run" these fix commands? Perhaps I overlooked the documentation for this.

Thank you

1
  • I am going to re-restore from the latest snapshot and attempt to start and sync the db sync node without "--consumed-tx-out" flag in run command. Seems as though the script used to process the consumed-tx-out update needs some more work.
    – Nicholas
    Feb 1 at 14:41

1 Answer 1

1

Snapshots use the default db-sync flavour, which doesn't enable the --consumed-tx-out flag. This flag creates the tx_out.consumed_by_tx_id column. Also for each tx_in entry it updates exactly one tx_out.consumed_by_tx_id field. The fact that there are so many updates and that postgres is not really optimised for updates makes this process very slow. Also note this flag eventually drops all tx_in entries, since they become redundant.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.