diff options
| author | Jim Posen <jimpo@coinbase.com> | 2018-03-08 10:57:26 -0800 |
|---|---|---|
| committer | Jim Posen <jimpo@coinbase.com> | 2018-04-25 11:25:19 -0700 |
| commit | 9b2704777ceeca48d57ce058ae91674c7764b143 (patch) | |
| tree | d9e46d97186ecba4b4be798a860937b343111627 /doc | |
| parent | ed77dd6b3052fd3b4191f8a17b682f0b24acf332 (diff) | |
[doc] Include txindex changes in the release notes.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/files.md | 1 | ||||
| -rw-r--r-- | doc/release-notes-pr13033.md | 11 |
2 files changed, 12 insertions, 0 deletions
diff --git a/doc/files.md b/doc/files.md index 2eac7ed664..5657b1e6cb 100644 --- a/doc/files.md +++ b/doc/files.md @@ -10,6 +10,7 @@ * db.log: wallet database log file; moved to wallets/ directory on new installs since 0.16.0 * debug.log: contains debug information and general logging generated by bitcoind or bitcoin-qt * fee_estimates.dat: stores statistics used to estimate minimum transaction fees and priorities required for confirmation; since 0.10.0 +* indexes/txindex/*: optional transaction index database (LevelDB); since 0.17.0 * mempool.dat: dump of the mempool's transactions; since 0.14.0. * peers.dat: peer IP address database (custom format); since 0.7.0 * wallet.dat: personal wallet (BDB) with keys and transactions; moved to wallets/ directory on new installs since 0.16.0 diff --git a/doc/release-notes-pr13033.md b/doc/release-notes-pr13033.md new file mode 100644 index 0000000000..3ab4a984db --- /dev/null +++ b/doc/release-notes-pr13033.md @@ -0,0 +1,11 @@ +Transaction index changes +------------------------- + +The transaction index is now built separately from the main node procedure, +meaning the `-txindex` flag can be toggled without a full reindex. If bitcoind +is run with `-txindex` on a node that is already partially or fully synced +without one, the transaction index will be built in the background and become +available once caught up. When switching from running `-txindex` to running +without the flag, the transaction index database will *not* be deleted +automatically, meaning it could be turned back on at a later time without a full +resync. |