Managed instance of the PostgreSQL database server.


  • PostgreSQL server (9.5, 9.6, 10, 11, 12, or 13)


Managed PostgreSQL instances already have a production-grade configuration with reasonable sized memory parameters (for example, shared_buffers, work_mem).


Putting custom configuration in /etc/local/postgresql/VERSION/*.conf doesn’t work properly on 20.09 and should not be used anymore. Some options from there will be ignored silently if they are already defined by our platform code. Use NixOS-based custom config as described below instead.

You can override platform and PostgreSQL defaults by using the services.postgresql.settings option in a custom NixOS module. Place it in /etc/local/nixos/postgresql.nix, for example:

{ config, pkgs, lib, ... }:
  services.postgresql.settings = {
      log_connections = true;
      huge_pages = "try";
      max_connections = lib.mkForce 1000;

To override platform defaults, use lib.mkForce before the wanted value to give it the highest priority.

String values will automatically be enclosed in single quotes. Single quotes will be escaped with two single quotes. Booleans in Nix (true/false) are converted to on/off in the PostgreSQL config.

Run sudo fc-manage -b to activate the changes (restarts PostgreSQL!).

See Custom NixOS-native configuration for general information about writing NixOS modules.


Service users can use sudo -u postgres -i to access the PostgreSQL super user account to perform administrative commands like createdb and createuser.

Both service users and the postgres DB super user may invoke sudo fc-manage --build to apply configuration changes and restart the PostgreSQL server (if necessary).


The default monitoring setup checks that the PostgreSQL server process is running and that it responds to connection attempts to the standard PostgreSQL port.


Our PostgreSQL installations have the autoexplain feature enabled by default.