# gh-ost を Homebrew, Nix でインストール gh-ost のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:gh-ost ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install gh-ost ``` 証拠: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#gh-ost ``` 証拠: nixpkgs package indexes: pkgs/by-name/gh/gh-ost/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## パッケージ情報 - **パッケージキー:** brew:gh-ost - **パッケージマネージャ:** Homebrew - **バージョン:** 1.1.10 - **ソース概要:** Triggerless online schema migration solution for MySQL - **ホームページ:** - **リポジトリ:** - **最終更新:** 2026-07-29T16:05:00+02:00 - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - gh-ost (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 1.1.10 ## プロジェクトの歴史と使われ方 gh-ost is GitHub's triggerless online schema-migration tool for MySQL, designed to move table changes through binlog streaming rather than database triggers. ### プロジェクトの歴史 GitHub created the gh-ost repository in March 2016 and published pre-production releases beginning with v0.7 in May 2016. The README explains that the name began as `gh-osc`, for GitHub Online Schema Change, before becoming `gh-ost`, and credits GitHub's database infrastructure team as designers, authors, reviewers, and testers. The project came out of GitHub's operational experience with MySQL schema changes at production scale. Its design follows the ghost-table migration pattern used by earlier online schema-change tools, but replaces trigger-based change capture with MySQL binary-log streaming so the tool can pause, throttle, audit, and control cut-over more explicitly. ### 採用の歴史 gh-ost became significant beyond GitHub because it offered a production-tested alternative to pt-online-schema-change and Facebook's online schema-change lineage. Its documentation includes cloud and managed-database notes, test-on-replica guidance, interactive commands, hooks, and operational limits, making it attractive to teams that needed safer MySQL DDL changes. ### 使われ方 Practitioners run gh-ost in noop, replica test, replica-assisted master migration, direct master migration, or replica-only modes. Common practice is to test on replicas, run a noop check, execute the migration, watch throttling and lag controls, and postpone cut-over until an operator chooses the swap window. ### パッケージ好きにとっての重要性 For package-manager users, gh-ost matters because it turns a sophisticated database migration workflow into a single Go binary available through releases and packages. That makes online schema migration scriptable in deployment pipelines while keeping the operational controls visible at the command line. ### タイムライン - 2016: The GitHub repository was created. - 2016: v0.7 was published as a pre-production release. - 2016: GitHub published an engineering article describing gh-ost as its online migration tool for MySQL. - 2026: The release feed showed the v1.1 series. ### Related projects - The README explicitly relates gh-ost to Facebook online schema change and Percona's pt-online-schema-change, while highlighting its triggerless binlog-based design. ### ソース - - - - - - - ## セキュリティノート broad file, network, media, or database tool signal. - **Geiger リスク:** blue / 中 - broad file, network, media, or database tool signal ## 他のパッケージマネージャ記録 - Nix - gh-ost: normalized package name match | nixpkgs package indexes: pkgs/by-name/gh/gh-ost/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/gh-ost.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gh-ost.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph