rebuilddb2

README

Command line app rebuilddb2

The rebuilddb2 app is used for maintenance of fnodata's fnopg database that uses PostgreSQL to store a nearly complete record of the Fonero blockchain data.

IMPORTANT: When performing a bulk data import (e.g. full chain scan from genesis block), be sure to configure PostgreSQL appropriately. Please see postgresql-tuning.conf for tips.

Installation

Be able to build fnodata (see ../../README.md). In short:

• Install dep, the dependency management tool

  go get -u -v github.com/golang/dep/cmd/dep
  

• Clone the fnodata repository

  git clone https://github.com/fonero-project/fnodata $GOPATH/src/github.com/fonero-project/fnodata
  

• Populate vendor folder with dep ensure

  cd $GOPATH/src/github.com/fonero-project/fnodata
  dep ensure
  

• Build rebuilddb2

  # build rebuilddb2 executable in workspace:
  cd $GOPATH/src/github.com/fonero-project/fnodata/cmd/rebuilddb2
  go build
  # or to install fnodata and other tools into $GOPATH/bin:
  go install ./cmd/rebuilddb2
  

Usage

First edit rebuilddb2.conf, using sample-rebuilddb2.conf to start. You will need to follow a typical PostgreSQL setup process, creating a new database/scheme and a new role that has permissions/owns that database.

A fresh rebuild of the database is accomplished via:

./rebuilddb2 -D  # drop any existing tables
./rebuilddb2     # rebuild tables from scratch

Remember to update your PostgreSQL config (postgresql.conf) before and after bulk data imports. Namely, before normal fnodata operation, ensure that fsync=true and other setting are adjusted for efficient queries.

Details

Rebuilding the fnodata tables from scratch involves the following steps:

• Connect to the PostgreSQL database using the settings in rebuilddb2.conf
• Create the tables (i.e. "blocks", "transactions", "vins", etc).
• Starting from genesis block, process each block and store in tables.
• Create indexes for each table.

See rebuilddb2 --help for more information on how to tweak the operating mode.

License

See LICENSE at the base of the fnodata repository.