Add pagination to /matches
#96
Assignees
Milestone
Comments
KtorZ
added a commit
that referenced
this issue
Jan 3, 2023
The goal is to allow client fetching smaller response, but not necessarily to use the range to make query faster. We gain some performance improvement from the fact that the database will yield less results, but the queries are extended in a way that the slot range has no effect whatsoever on the query planner. This is because, we generally want to keep searching by address, payment credential, output reference and so on, and not drop those indexes for a dumb query on the created_at index. Indeed, imagine we query a specific output reference from the database, but only after slot 5M; now there might still be millions of results after that slot, so we don't want the database to only filter results by slot and then, scan what's left to find the output. We'd rather find the candidate outputs, and then, discard those that aren't within the given slot range. Fixes #96
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #75
Originally posted by cortsf October 17, 2022
Describe your idea, in simple words.
Add limit or proper pagination parameters to the
/matchesendpoint.Why is it a good idea?
It would allow us to index an oracle. We only need the most recent values.
Are you willing to work on it yourself?
Probably. We are looking to pick a chain indexer for our project without having to extend it if possible.
The text was updated successfully, but these errors were encountered: