pkg.soopen package index

brew / Rang 5647

pgsync mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für pgsync in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install pgsync

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#pgsync

nixpkgs package indexes · pkgs/by-name/pg/pgsync/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Sync Postgres data between databases

Befehle und Aliase

  • pgsync

Verlauf

Projektgeschichte und Nutzung

pgsync is a Ruby-based command-line utility for synchronizing PostgreSQL data between databases with parallel transfer, selective copying, safety controls, and data masking.

Projektgeschichte

Andrew Kane released pgsync in December 2015 as a Ruby command-line tool inspired by heroku-pg-transfer.

It evolved from basic database copying into a parallel synchronization tool with partial-table selection, schema operations, resumable batching, framework integrations, safety restrictions, and server-side sensitive-data transformations.

Adoptionsgeschichte

The official README describes pgsync as battle-tested at Instacart.

The tool is distributed through RubyGems, Homebrew, Docker, and Nix, and its changelog records continued compatibility work across Ruby, PostgreSQL, and packaging environments.

Wie es verwendet wird

Running `pgsync --init` in a project creates `.pgsync.yml`; named database configurations use `.pgsync-<database>.yml`. Commands search from the working directory through parent directories for configuration.

Users can synchronize all data, selected tables, filtered records, or named groups; optionally preserve or truncate destination rows, transfer schemas, defer constraints, and resume large append-only backfills.

Data rules can replace or null sensitive fields on the source server, and the destination is restricted to localhost by default unless explicitly marked safe.

Warum Paket-Nerds sich dafür interessieren

pgsync occupies the practical middle ground between full database dumps and application-specific seed scripts: it can copy selected tables, filtered rows, and related record groups while handling schema differences.

Its server-side data rules are especially significant for developers who need production-like local datasets without allowing sensitive values to leave the source database.

Zeitleiste

  • 2015-12-07: Version 0.1.0, the first release.
  • 2016: Added richer groups, partial-row synchronization, wildcard tables, and batch transfers.
  • 2020: Added Django and Laravel integrations, parallel jobs, trigger controls, and Amazon RDS support.
  • 2024-07-10: Version 0.8.0 added a Linux ARM64 Docker image.

Related projects

  • The project credits heroku-pg-transfer as an inspiration.
  • Its README points to pgslice, Dexter, and PgHero as related PostgreSQL tools.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:sync,database

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 2 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
.pgsync.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
.pgsync.yml.pgsync-<database>.yml
Windows
.pgsync.yml.pgsync-<database>.yml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
pgsynccliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-09-19
Manager-Version0.8.1
Manager aktualisiert2026-09-13
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.8.1

https://github.com/ankane/pgsync

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:pgsync
Version0.8.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/pgsync
Homepagehttps://github.com/ankane/pgsync
Repositoryhttps://github.com/ankane/pgsync
LizenzMIT
Quellarchivhttps://github.com/ankane/pgsync/archive/refs/tags/v0.8.1.tar.gz
Zuletzt aktualisiert2026-09-13T11:35:57Z
Pulseupdated
Abhängigkeitenlibpq, ruby
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namepgsync
Version Scheme0
Revision1
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

pgsync

nix profile install nixpkgs#pgsync
  • normalized package name match
  • Abgeglichen nach: Pgsync
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/pg/pgsync/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation