Default expectation safe interface. Equivalent to

  with = withConfig defaultConfig

Exception safe database create with options. See startConfig for more details. Calls stop even in the face of exceptions.

Exception safe version of restart

Default start behavior. Equivalent to calling startConfig with the defaultConfig

Create zero or more temporary resources and use them to make a Config.

The passed in config is inspected and a generated config is created. The final config is built by

  generated <> extra

Returns a DB that requires cleanup. startConfig should be used with a bracket and stop, e.g.

  withConfig :: Config -> (DB -> IO a) -> IO (Either StartError a)
  withConfig plan f = bracket (startConfig plan) (either mempty stop) $
     either (pure . Left) (fmap Right . f)

or just use withConfig. If you are calling startConfig you probably want withConfig anyway.

Based on the value of socketClass a "postgresql.conf" is created with

  listen_addresses = 'IP_ADDRESS'

if it is IpSocket. If is UnixSocket then the lines

  listen_addresses = ''
  unix_socket_directories = 'SOCKET_DIRECTORY'

are added.

Additionally the generated Config also does the following: * Sets a connectionTimeout of one minute. * Logs internal Events. * Sets the processes to use the standard input and output handles. * Sets the dataDirectoryString to file path generated from dataDirectory

All of these values can be overrided by the extra config.

Stop the postgres process and cleanup any temporary resources that might have been created.

Restart the postgres from DB using the prior Plan

Only stop the postgres process but leave any temporary resources. Useful for testing backup strategies when used in conjunction with restart or withRestart.

Handle for holding temporary resources, the postgres process handle and postgres connection information. The DB also includes the final plan used to start initdb, createdb and postgres. See toConnectionString or toConnectionOptions for converting a DB to postgresql connection string.

Convert a DB to a connection string. Alternatively one can access the Options using toConnectionOptions

Convert a DB to a connection Options type.

Access the data directory. This was either generated or specified explicitly when creating the Config

Get the directory that is used to create other temporary directories

Make the data directory permanent. Useful for debugging. If you are using with or withConfig this function will not modify the DB that is passed for cleanup. You will need to setup your own bracket like

   bracket (fmap makeDataDirPermanent start) (either mempty stop)

Reload the configuration file without shutting down. Calls pg_reload_conf().

Display a DB

A list of failures that can occur when starting. This is not and exhaustive list but covers the errors that the system catches for the user.

The default configuration. This will create a database called "postgres" via initdb (it's default behavior). It will create a temporary directory for the data and a temporary directory for a unix socket on a random port. Additionally it will use the following "postgresql.conf" which is optimized for performance.

   shared_buffers = 12MB
   fsync = off
   synchronous_commit = off
   full_page_writes = off
   log_min_duration_statement = 0
   log_connections = on
   log_disconnections = on
   client_min_messages = ERROR

defaultConfig also passes the --no-sync flag to initdb.

If you would like to customize this behavior you can start with the defaultConfig and overwrite fields or combine a defaultConfig with another Config using <> (mappend).

Alternatively you can eschew defaultConfig altogether, however your postgres might start and run faster if you use defaultConfig.

The defaultConfig also disables the logging of internal Events.

To append additional lines to "postgresql.conf" file create a custom Config like the following.

 custom = defaultConfig <> mempty
   { plan = mempty
     { postgresConfigFile =
         [ "wal_level = replica"
         , "archive_mode = on"
         , "max_wal_senders = 2"
         , "fsync = on"
         , "synchronous_commit = on"
         ]
     }
   }

Or using the provided lenses and your favorite lens library

 custom = defaultConfig & planL . postgresConfigFile <>~
   [ "wal_level = replica"
   , "archive_mode = on"
   , "max_wal_senders = 2"
   , "fsync = on"
   , "synchronous_commit = on"
   ]

This is common enough there is defaultPostgresConf which is a helper to do this.

As an alternative to using defaultConfig one could create a config from connections parameters using optionsToDefaultConfig

mappend the defaultConfig with a Config that provides additional "postgresql.conf" lines. Equivalent to

defaultPostgresConf extra = defaultConfig <> mempty
  { plan = mempty
    { postgresConfigFile = extra
    }
  }

or with lenses

defaultPostgresConf extra = defaultConfig & planL . postgresConfigFile <>~ extra

The standardProcessConfig sets the handles to stdin, stdout and stderr and inherits the environment variables from the calling process.

The same as defaultConfig but all the handles are set to "/dev/null". See silentProcessConfig as well.

silentProcessConfig sets the handles to "/dev/null" and inherits the environment variables from the calling process

Attempt to create a Config from a Options. Useful if you want to create a database owned by a specific user you will also login with among other use cases.