Page MenuHomePhabricator

Straighten out replication/cache behavior in "bin/storage dump"
ClosedPublic

Authored by epriestley on Aug 28 2019, 3:19 PM.
Tags
None
Referenced Files
F19908979: D20743.id.diff
Wed, Apr 1, 10:52 PM
F19830606: D20743.diff
Tue, Mar 10, 2:31 PM
F19830578: D20743.id49458.diff
Tue, Mar 10, 2:20 PM
F19830134: D20743.id49459.diff
Tue, Mar 10, 10:55 AM
F19829590: D20743.id49459.diff
Tue, Mar 10, 7:01 AM
F19092782: D20743.id49458.diff
Dec 3 2025, 6:27 PM
F18985183: D20743.id.diff
Nov 17 2025, 12:55 PM
F18854735: D20743.diff
Nov 1 2025, 12:31 AM
Subscribers
None

Details

Summary

Fixes T13336.

  • Prevent --no-indexes from being combined with --for-replica, since combining these options can only lead to heartbreak.
  • In --for-replica mode, dump caches too. See discussion in T13336. It is probably "safe" to not dump these today, but fragile and not correct.
  • Mark the "MarkupCache" table as having "Cache" persistence, not "Data" persistence (no need to back it up, since it can be fully regenerated from other datasources).
Test Plan

Ran bin/storage dump with various combinations of flags.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Aug 28 2019, 3:25 PM
This revision was automatically updated to reflect the committed changes.