wownero

Author	SHA1	Message	Date
Jesus Ramirez	f9b3f6ef3b	Removed Berkeley DB and db switching logic	5 years ago
moneromooo-monero	eda2661aa2	Allow pruning before v10 This check is now not needed anymore, and would prevent people from using --prune-blockchain when starting a new sync	5 years ago
moneromooo-monero	1c9d5285d1	blockchain_prune: don't prune before v10 This uses system time since it doesn't see the p2p network, so is not 100% accurate	5 years ago
moneromooo-monero	b750fb27b0	Pruning The blockchain prunes seven eighths of prunable tx data. This saves about two thirds of the blockchain size, while keeping the node useful as a sync source for an eighth of the blockchain. No other data is currently pruned. There are three ways to prune a blockchain: - run monerod with --prune-blockchain - run "prune_blockchain" in the monerod console - run the monero-blockchain-prune utility The first two will prune in place. Due to how LMDB works, this will not reduce the blockchain size on disk. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. The third way will create a second database, a pruned copy of the original one. Since this is a new file, this one will be smaller than the original one. Once the database is pruned, it will stay pruned as it syncs. That is, there is no need to use --prune-blockchain again, etc.	6 years ago