Implement retry system

Open
#143 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, postgresql
Domain
cli, databases

Research direction

Start by tracing the plan-generation and CLI entry points, then identify how migration statements and lock-timeout failures are represented. The issue is done when statements can expose retry specifications that clients configure, and the CLI uses those specifications to retry eligible operations.

Written by the indexing model from the issue text.

Description

Even some fast-running migration statements need to acquire a an ACCESS_EXCLUSIVE_LOCK to update the table metadata. Acquiring this lock can be very tricky on high throughput databases, and it may transiently fail given a strict enough lock timeout. We should:

Plan generation: Define retry specs on some statements, where clients can determine if and how they want to retry
CLI: Implement a retry system that leverages the retry specs

Dominant language
Go
Stars
884
Forks
82
No merged PRs in 30d

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.

More from stripe/pg-schema-diff

All issues in stripe/pg-schema-diff

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.