graphprotocol / graphprotocol/graph-node

Graphman copy indexing optimizations

Open
#5,140 2 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

  • #5364 by @zorancv — closed without merging
area/graphman ops
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

To reduce the size of a DB shard without downtime, graphman copying deployments out is a good option. But it needs a few optimizations to be usable en masse, including on index creation. This track two of those optimizations:

  1. Create the indexes based on the index creation DDL of the source, not based on the default.
  2. Create the BTree indexes after the copy is done, and only the GiST afterwards.

@incrypto32 will mentor @itsjerryokolo on this task.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.