pg_crash
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
pg_crash | 1.0 | ADMIN | BSD-3-Clause | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 5210 | pg_crash | No | Yes | Yes | No | No | No | - |
| Related | pg_dirtyread pg_savior pg_cheat_funcs |
|---|
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | PIGSTY | 1.0 | 1817161514 | pg_crash | - |
| RPM | PIGSTY | 1.0 | 1817161514 | pg_crash_$v | - |
| DEB | PIGSTY | 1.0 | 1817161514 | postgresql-$v-pg-crash | - |
Build
You can build the RPM / DEB packages for pg_crash using pig build:
Install
You can install pg_crash directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:
Install the extension using pig or apt/yum/dnf:
Preload:
Usage
pg_crash is a chaos engineering extension that periodically sends kill signals to PostgreSQL backend processes, useful for HA and failover testing. It must be added to shared_preload_libraries.
Configuration
Add to postgresql.conf:
Signal Reference
Common POSIX signals: 1 (SIGHUP), 2 (SIGINT), 3 (SIGQUIT), 9 (SIGKILL), 15 (SIGTERM).
After configuring, restart the server. The background worker will periodically send the configured signals to random backend processes at the specified interval.
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)