v4.2.1-alpha

What's Changed

• Use a specific tag while building migration tool by @prathamesh0 in #101

Full Changelog: v4.2.0-alpha...v4.2.1-alpha

v4.2.0-alpha

What's Changed

• Add block hash to primary keys in transactions, receipts and logs tables by @prathamesh0 in #100

Full Changelog: v4.1.4-alpha...v4.2.0-alpha

v4.1.4-alpha

What's Changed

• Update the go-version in build container by @abdulrabbani00 in #93

Full Changelog: v4.1.3-alpha...v4.1.4-alpha

v4.1.3-alpha

What's Changed

• Fix docker-compose for publishing image by @nikugogoi in #91

Full Changelog: v4.1.2-alpha...v4.1.3-alpha

v4.1.2-alpha

What's Changed

• Update startup_script.sh by @abdulrabbani00 in #84
• Update instructions and docker-compose files for simplified db setup by @prathamesh0 in #88
• Fix stored functions for in-place snapshot by @prathamesh0 in #87

Full Changelog: v4.1.1-alpha...v4.1.2-alpha

v4.1.1-alpha

What's Changed

• Use a single file to build and push a docker image by @abdulrabbani00 in #77
• Merge changes for docker process to build and push a docker image by @prathamesh0 in #78
• Run migrations on a single-node TimescaleDB setup by @prathamesh0 in #79

Full Changelog: v4.1.0-alpha...v4.1.1-alpha

v3.2.1-docker-test

Test the docker build and push within one step.

v4.1.0-alpha

What's Changed

• Add a table for watched addresses (v3) by @nikugogoi in #54
• Add known_gaps table by @abdulrabbani00 in #53
• update the pre- and post- batch sets with new meta schema and tables by @i-norden in #59
• Merge latest changes from main into sharding branch by @ashwinphatak in #76

New Contributors

• @nikugogoi made their first contribution in #54
• @abdulrabbani00 made their first contribution in #53
• @ashwinphatak made their first contribution in #76

Full Changelog: v4.0.1-alpha...v4.1.0-alpha

v4.0.1-alpha

What's Changed

• denormalize tables by block_number by @i-norden in #51
• v4.0.0 alpha by @i-norden in #56
• [v4] TimescaleDB support by @i-norden in #65
• Fixes + new schema dump by @i-norden in #67
• Remove foreign keys to hypertables and fix schema dump by @prathamesh0 in #70
• Multi-node setup to run the migrations by @prathamesh0 in #72
• Create distributed hypertables directly, skipping hypertables by @prathamesh0 in #74
• Update Dockerfile to run migrations by @prathamesh0 in #75

Full Changelog: v3.0.7...v4.0.1-alpha

v3.2.0

v3 Database Schema

The primary objective of this upgrade from v2 is to move from a serial int based primary/foreign key scheme to a deterministic natural key scheme, this helps facilitate horizontal scaling by avoiding serial key conflicts when merging separate databases.

We also introduce sets of migrations split into pre- and post- historical batch processing units. The pre- set forgoes all FK and unique constraints, indexes, and sets the tables as UNLOGGED. The post- set adds these constraints and indexes and sets the tables as LOGGED. This is to improve performance of historical batch processing.

Additionally,

• New eth_meta.known_gaps table
• New eth_meta.watched_addresses table
• New eth_meta schema
• Remove unique constraint on the receipt_cids.leaf_mh_key column, since we can (in theory) have duplicate receipts
• Adding some additional rows that will be useful for searches (e.g. header_cids.coinbase).
• Removing some that are not particularly useful for searches (e.g. header_cids.base_fee).
• Switching some BIGINT types to NUMERIC to avoid overflow.
• Typo fixes in file names.
• Split PK application to public.blocks into its own migration in the migrate_post_batch_set of migrations as we need to apply only that constraint prior to the v2 => v3 transformation.
• Split application of log_cids related indexes into separate migration for logTrie fix processing; disable afterwards for v2 => v3 transformation.
• Adjust migrations to (temporarily) apply log_cids.leaf_mh_key FK to ensure the logTrie fix was successful.
• New Makefile targets for running up migrations one at a time: migrate_up_by_one and migrate_post_batch_set_up_by_one.
• Fix issue where Makefile was failing to find goose if GOPATH was unset (#38).
• New table to track the current version of the database schema, the version corresponds with the semantic versioning of this release.

Full v2 => v3 changelog: release-v2.0.0...release-v3.2.0