Engine Reference

PostgreSQL 16 Guide

Key features, supported extensions, SSL requirements, and performance best practices on MQZZ.DB.

1. Mandatory SSL Connection Mode

To guarantee zero plaintext transmission over public internet backbones, our PostgreSQL cluster enforces SSL:

postgresql://USER:PASSWORD@sql.mqzz.site:5432/DBNAME?sslmode=require

If using ORMs (Prisma, TypeORM, Hibernate, SQLAlchemy), ensure the connection URL includes `?sslmode=require` or `{ ssl: { rejectUnauthorized: false } }`.

2. Connection Pooling & Limits

Each free database is configured with an active limit of 20 concurrent connections (`ALTER DATABASE ... CONNECTION LIMIT 20`).

• For traditional frameworks (Laravel, Django, Spring Boot): Keep persistent pool sizes between 3 and 10.

• For serverless architectures (AWS Lambda, Vercel Edge, Cloudflare Workers): Implement PgBouncer or client-side connection pooling to avoid exhausting the limit.

3. Optimizing Storage Under 5 GB

PostgreSQL features MVCC (Multi-Version Concurrency Control), meaning row updates generate dead tuples until autovacuum runs:

Run VACUUM ANALYZE; periodically after large batch deletion operations.
Avoid storing large binary blobs (images, videos) directly in bytea columns; store metadata in PostgreSQL and media on object storage (S3/R2).
Use appropriate data types: BIGINT or INTEGER over TEXT for IDs, and TIMESTAMPTZ for timestamps.