Skip to content

PT-1923: Replace offensive terminology (master/slave → primary/replica) in pt-pg-summary - #1161

Open
guriandoro wants to merge 1 commit into
percona:3.xfrom
guriandoro:PT-1923_pg_offensive_terminology
Open

PT-1923: Replace offensive terminology (master/slave → primary/replica) in pt-pg-summary#1161
guriandoro wants to merge 1 commit into
percona:3.xfrom
guriandoro:PT-1923_pg_offensive_terminology

Conversation

@guriandoro

Copy link
Copy Markdown
Collaborator

PT-1923: Offensive terminology elimination (Group 3, PostgreSQL)

Replaces master/slave with primary/replica across pt-pg-summary,
the only PostgreSQL-specific tool in the toolkit. All occurrences were the
tool's own naming — PostgreSQL itself never uses these terms; the SQL simply
aliased pg_is_in_recovery() as Is_Slave and read from pg_stat_replication.

Changes

  • Report output: Replicas and the lag with Primary, There are no replica hosts, Is Replica
  • lib/pginfo: ReplicaHosts96/10 fields, log/error strings
  • models/: IsReplica, SQL alias Is_Replica, slavehosts{10,96}.xo.goreplicahosts{10,96}.xo.go
  • models/gen.sh updated so xo regeneration reproduces the new names
  • Docs (README.rst, symlinked as docs/pt-pg-summary.rst)

No functional change. Verified: gofmt clean, go build, go vet pass.

Rename master/slave to primary/replica across the pt-pg-summary tool:
report output labels, the pginfo collector fields, the xo-generated
models (and models/gen.sh so a future regeneration stays consistent),
main.go, and the tool docs.

No behavior change: the underlying pg_is_in_recovery() and
pg_stat_replication queries are untouched; only identifiers, labels,
and comments change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant