[Main] Avoid slow transaction search with txindex enabled #395
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is no point in doing a "slow" search for a transaction if it isn't found in the txindex (if enabled).
ghost
assigned 
|
utACK |
|
ACK. |
presstab
added a commit
that referenced
this pull request
Nov 29, 2017
c507dc1 [Main] Avoid slow transaction search with txindex enabled (Fuzzbawls) Tree-SHA512: de1b78e8993b9e77015335bbd99f8716dacbf07313eeaae9ff4307703b15c8b746852052ab8d566b1418b1daf85513bf102719ed37b03691d44af8d7f363493e
Fuzzbawls
added a commit
to Fuzzbawls/PIVX
that referenced
this pull request
Nov 29, 2017
There is no point in doing a "slow" search for a transaction if it isn't found in the txindex (if enabled). Github-Merge: PIVX-Project#395 Rebased-From: c507dc1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is no point in doing a "slow" search for a transaction if it isn't
found in the txindex (if enabled).
We run with txindex enabled by default, so this could see some performance increase in the form of faster response times when searching for a transaction that doesn't exist.