Administration

Standard Operating Procedures (SOP) for database administration tasks

How to maintain existing PostgreSQL clusters with Pigsty?

This section provides standard operating procedures (SOP) for common PostgreSQL administration tasks:

SOP: Standard operating procedures for creating/removing clusters and instances, backup & restore, rolling upgrades, etc.
Failure: Common failure troubleshooting strategies and handling methods, such as disk exhaustion, connection exhaustion, XID wraparound, etc.
Drop: Emergency procedures for handling accidental data deletion, table drops, and database drops
Maintain: Maintenance tasks including regular inspections, post-failover cleanup, bloat management, VACUUM FREEZE, etc.
Tuning: Automatic optimization strategies and adjustment methods for memory, CPU, storage parameters, etc.

Common failures and analysis troubleshooting approaches

Database management: create, modify, delete, rebuild databases, and clone databases using templates

PostgreSQL and Pgbouncer HBA rule management operations: refresh, reload, verify, and troubleshoot.

Common PostgreSQL administration procedures in Pigsty for maintaining production database clusters.

Standard operation guide for creating/destroying PostgreSQL clusters and scaling existing clusters.

Creating PostgreSQL users/roles, managing connection pool roles, refreshing expiration times, user password rotation

Tuning Postgres Parameters

Handling accidental data deletion, table deletion, and database deletion

How to clone databases, database instances, and database clusters?

Common system maintenance tasks

How to upgrade (or downgrade) PostgreSQL minor version kernel, and how to perform major version upgrades

Feedback

Was this page helpful?

Thanks for the feedback! Please let us know how we can improve.