What is Checkpoint?

The original idea comes from the ARIES paper (see reference). For performance reason, database does not persist modified data to disk after every committed change, instead, it periodically issues checkpoint which persists the changes in batch. It's called checkpoint because when database crashes and then starts again for crash recovery, the recovery process only needs to recover the committed changes after the latest checkpoint because the checkpoint guarantees any commits before that checkpoint have been persisted already. Checkpoint is still a heavy operation and may impact database performance.

External reference

Database schema migration and version control, Database CI/CD, and DevOps for developers and DBAs

Bytebase is an open source, web-based database schema change and version control tool for teams. It offers a web-based collaboration workspace to help DBAs and Developers manage the lifecycle of application database schemas.

  • MySQL
  • PostgreSQL
  • Snowflake
  • Oracle
  • SQL Server
  • MongoDB
  • Redis
  • Redshift
  • ClickHouse
  • TiDB
  • OceanBase
  • Spanner
  • MariaDB
  • GitLab
  • GitHub
  • Bitbucket
  • Azure DevOps
  • Terraform


Subscribe to Newsletter

By subscribing, you agree with Bytebase's Terms of Service and Privacy Policy.