feat(postgres): optimize contract queries by splitting large data from metadata #105
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.
Fixes #95
Problem
Slow PostgreSQL queries (>1s) when fetching contract data due to 2MB rows with large BYTEA fields mixed with frequently queried metadata.
Solution
Split the contracts table into separate metadata and data tables to optimize query performance.
Changes
contract_metadataandcontract_datatablesidx_contract_metadata_statefor faster state filteringFiles Modified
src/storage/postgres/migrations/0004_split_contract_tables.{up,down}.sqlsrc/storage/sqlx.rs- Added new table structssrc/storage/postgres/mod.rs- Updated storage implementationExpected Performance
Query times should improve from >1s to <100ms by only loading metadata when contract data isn't needed.