<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <url>
        <loc>https://rillence.com/</loc>
    </url>
    <url>
        <loc>https://rillence.com/blog/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-activity-locks/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-api/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-autovacuum-bloat/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-dump-restore/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-explain-basics/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-explain-planner/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-indexes-btree/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-indexes-covering-partial/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-indexes-search/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-locks-deadlocks/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-migrations-columns/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-migrations-zero-downtime/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-mvcc-vacuum/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-pooling-basics/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-pooling-modes/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-replication/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-stat-statements/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-transactions-isolation/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/postgres-wal-pitr/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/psql-essentials/</loc>
    </url>
    <url>
        <loc>https://rillence.com/bricks/sql-investigation/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/cases/pg-missing-index/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/indexing/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/mysql-basics/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/new/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/on-call/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/query-performance/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/redis/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/goals/replication/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/settings/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/subscriptions/</loc>
    </url>
    <url>
        <loc>https://rillence.com/dashboard/team/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/getting-started/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/getting-started/installation/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/getting-started/quick-start/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/commands/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/configuration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/faq/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/hints/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/investigate/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/sandboxes/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/scenarios/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/scoring/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/the-repl/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/tracks/</loc>
    </url>
    <url>
        <loc>https://rillence.com/docs/postgres/troubleshooting/</loc>
    </url>
    <url>
        <loc>https://rillence.com/essentials/</loc>
    </url>
    <url>
        <loc>https://rillence.com/interview-prep/</loc>
    </url>
    <url>
        <loc>https://rillence.com/license/</loc>
    </url>
    <url>
        <loc>https://rillence.com/login/</loc>
    </url>
    <url>
        <loc>https://rillence.com/login/sso/</loc>
    </url>
    <url>
        <loc>https://rillence.com/notes/</loc>
    </url>
    <url>
        <loc>https://rillence.com/notes/autovacuum-quiet-process/</loc>
        <lastmod>2026-04-14</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/connection-pools-more-is-not-more/</loc>
        <lastmod>2026-05-20</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/incidents-start-before-postgres/</loc>
        <lastmod>2026-05-29</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/postgres-locks-alter-table/</loc>
        <lastmod>2026-04-25</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/postgres-monitoring-signal-vs-noise/</loc>
        <lastmod>2026-04-09</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/reliability-not-learned-from-docs/</loc>
        <lastmod>2026-03-27</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/schema-migrations-in-production/</loc>
        <lastmod>2026-04-19</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/slow-query-is-a-symptom/</loc>
        <lastmod>2026-04-04</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/standby-does-not-save-you/</loc>
        <lastmod>2026-05-12</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/notes/wal-and-checkpoints/</loc>
        <lastmod>2026-05-04</lastmod>
    </url>
    <url>
        <loc>https://rillence.com/paths/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/backend-engineer-path/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/backup-and-recovery/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/capstone-incident-control/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/connection-pooling/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/dba-path/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/diagnose-a-slow-endpoint/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/ha-and-failover/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/incident-response-readiness/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/indexing-mastery/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/interview-prep/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/live-diagnostics/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/locks-and-concurrency/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/multi-tenant-operations/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/postgres-internals/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/postgresql-foundations/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/production-readiness/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/reading-query-plans/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/replication-and-wal/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/safe-migrations/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/security-and-access/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/sre-on-call-path/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/storage-pressure/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/vacuum-and-bloat/</loc>
    </url>
    <url>
        <loc>https://rillence.com/paths/zero-downtime-operations/</loc>
    </url>
    <url>
        <loc>https://rillence.com/postgres/</loc>
    </url>
    <url>
        <loc>https://rillence.com/pricing/</loc>
    </url>
    <url>
        <loc>https://rillence.com/privacy/</loc>
    </url>
    <url>
        <loc>https://rillence.com/ride/</loc>
    </url>
    <url>
        <loc>https://rillence.com/roadmap/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/advisory-lock-forgotten/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/alter-table-locks-production/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/app-connected-to-stale-shadow-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/app-database-down-default-healthy/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/app-retry-connection-storm/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/archive-command-failure/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/archive-directory-backlog/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/audit-trail-missing/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/autovacuum-starvation-in-tenant-db/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/backup-before-rejoin/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/backup-restore-drill/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/backup-restore-under-pressure/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/backup-skipped-one-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/backup-target-full/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/backward-incompatible-migration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/bad-migration-and-lock-pileup/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/bad-nullable-column-rollout/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/base-backup-missing-wal/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/blocking-transaction/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/broken-replication-credentials/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/checkout-meltdown/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/checkout-slow-query-and-connection-storm/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/connected-to-wrong-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/connection-storm-after-deploy/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/create-index-without-concurrently-migration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/create-index-without-concurrently/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/database-ownership-privileges-mismatch/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/dead-tuples-growth/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/deadlock/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/default-privileges-surprise/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/disk-full-from-temp-files/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/expand-contract-migration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/failed-create-index-concurrently/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/failed-failover-due-to-lag/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/failover-pressure/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/failover-with-slot-cleanup/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/final-production-incident/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/freeze-age-warning/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/gin-index-misuse/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/hot-row-contention/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/idle-connection-leak/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/idle-in-transaction/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/index-bloat-after-churn/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/lock-queue-amplification/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/log-file-growth/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/long-transaction-blocks-ddl/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/long-transaction-prevents-cleanup/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/low-selectivity-index/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/manual-replica-promotion/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/migration-applied-to-one-tenant-only/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/migration-applied-to-wrong-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/missing-connect-privilege-on-target-db/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/missing-index/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/missing-trigram-index/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/n-plus-one-query-pattern/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/old-primary-returns/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/overprivileged-application-role/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/oversized-max-connections/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/partial-index-opportunity/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/partial-tenant-migration-outage/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/per-database-connection-limit-reached/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/pg-hba-blocks-application/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/pg-wal-disk-pressure/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/pgbouncer-pool-exhausted/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/pgbouncer-saturation-and-retry-storm/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/pitr-gap-detected/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/pool-size-misconfiguration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/post-failover-validation/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/prepared-statements-vs-pooling/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/primary-crash-and-stale-read-endpoint/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/primary-crash-detection/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/read-replica-stale-reads/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/read-write-endpoint-confusion/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/recovery-crisis/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/reindex-needed/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/release-fallout/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/replica-lag-stopped-replica/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/replica-query-conflict/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/replication-slot-dropped/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/restore-to-wrong-target/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/restore-wrong-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/rls-policy-mistake/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/runaway-query-holds-pool-connection/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/same-role-different-privileges-per-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/schema-drift-between-tenant-databases-migration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/schema-drift-between-tenant-databases/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/search-path-risk/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/security-misconfig-after-release/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/serializable-retry-storm/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/slow-count-pagination/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/split-brain-risk/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/ssl-requirement-mismatch/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/stale-statistics/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/storage-pressure-and-autovacuum-failure/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/synchronous-replication-latency/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/table-bloat-after-update-churn/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/tablespace-full/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/timeline-divergence-detected/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/too-many-connections/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/transaction-pooling-surprise/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/unmonitored-replication-slot-lag/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/unsafe-vacuum-full-capstone/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/user-has-access-to-wrong-database/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/vacuum-cost-delay-misconfiguration/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/vacuum-full-lock/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/vacuum-starvation-and-slow-queries/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/wal-explosion-replication-slot/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/wal-generation-spike/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/wal-pressure-and-replica-lag/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/work-mem-sort-spill/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/wrong-composite-index-order/</loc>
    </url>
    <url>
        <loc>https://rillence.com/scenarios/xid-wraparound-emergency-simulation/</loc>
    </url>
    <url>
        <loc>https://rillence.com/terms/</loc>
    </url>
</urlset>
