PostgreSQL is now a first-class database on PicoPaaS
Every app can now pick managed PostgreSQL or MySQL as an equal choice, with its own database, CA-verified TLS and engine-aware quotas.
We just shipped managed PostgreSQL, sitting next to MySQL as an equal choice. Tick Database, pick an engine, and the platform provisions a dedicated database and login role for your app, same isolation model as MySQL.
What you get
- CA-verified TLS: the server requires TLS and you can verify it with
sslmode=verify-fullagainst the CA the platform hands you. - The same
${{ db.* }}refs for both engines, so your env mapping barely changes. - Engine-aware quotas. At the 50 MB cap a Postgres role goes read-only and sessions are closed (you can still DELETE, TRUNCATE and DROP). At 2x the cap, CONNECT is revoked until you are back under.
- No
sql_require_primary_keyclash, which was what kept some apps off MySQL.
Honest limits
Each app role is capped at 5 connections (MySQL gets 10), because we run the cheapest single-node Postgres, so keep your pool small. The engine is fixed once the database exists. Specs that omit the engine still get MySQL.
resources:
db: true
db_engine: pg # mysql | pg
The User Guide now has an engine comparison table to help you choose. This closes out request 0006.