Tag

#postgresql

4 articles: System, Note.

← All tags

  1. Scale Breaking Points in Data-Intensive Systems

    As data load grows, where does boring architecture break? Working set, read replicas, partitioning, write load and a separate data layer — the breaking points in order, and what each one costs

  2. A PostgreSQL Backup Strategy with pgBackRest

    pg_dump alone is not a backup. A PITR-capable, compressed, verifiable backup architecture with pgBackRest

  3. Multiple Projects on a Single VPS

    One VPS, several independent apps. Deliberate minimalism over Kubernetes: user isolation, separate PHP-FPM pools, shared PostgreSQL/Redis, a plain deploy.

  4. Multiple DB Users with pgBouncer auth_query

    A practical setup for dynamic user authentication via `auth_query` instead of `userlist.txt` when running pgBouncer