Operations and limits
Connections, memory, monitoring and the audit log.
View as MarkdownConnections before memory
On a single-server platform, connections run out first. PostgreSQL reserves connections for the superuser, each role carries its own limit, and nothing enforces that the sum of those limits fits. The telemetry endpoint reports the sum of role limits and the amount of over-commitment; the journal records a warning when a limit is created or raised past the budget.
Memory is a hard ceiling
Container memory limits are enforced by the kernel without swap. Exceeding one terminates the container. Size limits from measured usage under load and leave headroom.
Logs, two kinds
Application and function output is a live stream over a realtime channel. The audit log is a durable, attributed record of control-plane mutations. They answer different questions and are stored differently.
What the audit log does not cover
It records platform mutations, not row changes inside your own tables. Data history is something you design with triggers or an append-only table, because only you know which changes matter.