You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The consumed migration happens on a single db-transaction, which is the same transaction where the consumed_by_tx_in_id column is created. This happens because otherwise there would be partial migrations that can cause problems. This migration also takes multiple hours (up to 24) and if it is interrupted it needs to be restarted from scratch. We could save progress on a new table. This requires schema changes so it needs a major bump, eg 13.2.
After #1416 there are some remaining issues that can improve the consumed and prune migrations. We split them in two lists.
Issues that affect users:
consumed
migration happens on a single db-transaction, which is the same transaction where theconsumed_by_tx_in_id
column is created. This happens because otherwise there would be partial migrations that can cause problems. This migration also takes multiple hours (up to 24) and if it is interrupted it needs to be restarted from scratch. We could save progress on a new table. This requires schema changes so it needs a major bump, eg 13.2.cardano-db-sync --rollback-to-slot
afterconsumed-tx-out
is bugged #1597Internal issues/tech debts:
ExtraMigrations
simplified and renamed #1489The text was updated successfully, but these errors were encountered: