Terms of Use for PGSizer PostgreSQL 17 & PgBouncer Calculators
Review the engineering disclaimer and vendor pricing verification rules governing PGSizer postgresql.conf and pgbouncer.ini configuration outputs. (Revision: 2026-11-12)
PGSizer Configuration Outputs Provided Strictly for Staging Validation
-
All postgresql.conf GUC settings, pgbouncer.ini pool definitions, SQL partitioning snippets, and NVMe storage projections generated by PGSizer are supplied on an "AS IS" mathematical reference basis without warranty.
Real-world PostgreSQL 17 memory consumption depends on query planner fan-out, custom C extensions, Linux vm.overcommit_memory sysctls, and index bloat. DBAs using PGSizer must validate every generated directive in a non-production staging environment prior to production reload.
External Hosting Contracts & 2026-11-12 Rate Snapshot Notice on PGSizer
-
PGSizer is not a hosting reseller or managed database vendor. Any KVM VPS, Dedicated VDS, or bare-metal server leased after clicking a PGSizer /go/* link is governed exclusively by your contract with Hostinger, Vultr, UltaHost, InterServer, or ChemiCloud, where public rates retrieved 2026-11-12 remain subject to upstream revision.
DBA Operational Responsibility & Limitation of Liability for PGSizer
-
Database administrators retain sole responsibility for pg_hba.conf network ACLs, TLS encryption, SCRAM-SHA-256 credentials, and verified WAL-G/pgBackRest restore drills. PGSizer Editorial Desk and PGSizer assume zero liability for data loss, OOM events, or third-party billing disputes.