< bitcoin-git> [bitcoin] lowogo opened pull request #19451: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/19451
< bitcoin-git> [bitcoin] lowogo closed pull request #19451: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/19451
< bitcoin-git> [bitcoin] MarcoFalke pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/8783bcc099e9...171f4a516bd6
< bitcoin-git> bitcoin/master 8f1bcf8 Andrew Chow: walletdb: Combine VerifyDatabaseFile and VerifyEnvironment
< bitcoin-git> bitcoin/master 91d1091 Andrew Chow: walletdb: Move PeriodicFlush into WalletDatabase
< bitcoin-git> bitcoin/master d8e9ca6 Andrew Chow: walletdb: Move Rewrite into BerkeleyDatabase
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #19324: wallet: Move BerkeleyBatch static functions to BerkeleyDatabase (master...bdb-batch-rm-statics) https://github.com/bitcoin/bitcoin/pull/19324
< sipa> [A
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/171f4a516bd6...f4301e910792
< bitcoin-git> bitcoin/master a76dafa Hennadii Stepanov: ci: Add tsan suppression for race in BerkeleyBatch
< bitcoin-git> bitcoin/master f4301e9 MarcoFalke: Merge #19450: ci: Add tsan suppression for race in BerkeleyBatch
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #19450: ci: Add tsan suppression for race in BerkeleyBatch (master...200705-tsan-bd) https://github.com/bitcoin/bitcoin/pull/19450
< phantomcircuit> why does the txindex and blockfilter index try to "keep in sync" why not just check every block in the currently active chain when we start and then deal with changes? they both use leveldb so can easily tell a consumer whether they have that particular block in the index
< phantomcircuit> i guess for txindex it would be kind of annoying to have a partial index
< luke-jr> phantomcircuit: I'm not clear what you're suggesting to do different
< phantomcircuit> luke-jr, at least for the block filter index, instead of keeping track of the "tip" just walk the current chain and try to rebuild
< phantomcircuit> it makes something that's O(1) O(n) but it means it's more flexible
< sipa> phantomcircuit: it's not clear to me how that would be practically different
< sipa> you mean how you could have some blocks indexed and others not?
< sipa> on an individual basis?