Handle for holding temporary resources, the postgres process handle and postgres connection information. The DB also includes the final Plan that was used to start initdb, createdb and postgres.

Default expectation safe interface. Equivalent to withPlan the defaultConfig

Exception safe default database create. Takes an action continuation which is given a DB it can use to connect to (see toConnectionString or postgresProcessClientConfig). All of the database resources are automatically cleaned up on completion even in the face of exceptions.

Default start behavior. Equivalent to calling startWith with the defaultConfig

Create temporary resources and use them to make a Config. The generated Config is combined with the passed in extraConfiguration to create a Plan that is used to create a database. The output DB includes references to the temporary resources for cleanup and the final plan that was used to generate the database and processes

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

The default configuration. This will create a database called "test" and create a temporary directory for the data and a temporary directory for a unix socket on a random port. If you would like to customize this behavior you can start with the defaultConfig and overwrite fields or combine the Config with another config using <> (mappend). If you would like complete control over the behavior of initdb, postgres and createdb you can call the internal function initPlan directly although this should not be necessary.

Restart the postgres using the Plan from the DB (e.g. resourcesPlan . dbResources)

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

Exception safe version of restart

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

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

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 high level options for overriding default behavior.

Lastoid is helper for overriding configuration values. It's Semigroup instance let's one either combine the a of two Lastoids using <> via the Mappend constructor or one can wholly replace the value with the last value using the Replace constructor. Roughly

  x <> Replace y = Replace y
  Replace x <> Mappend y = Replace (x <> y)
  Mappend x <> Mappend y = Mappend (x <> y)

A type to track whether a file is temporary and needs to be cleaned up.

The monoidial version of DirectoryType. Used to combine overrides with defaults when creating a DirectoryType. The monoid instance treats PTemporary as mempty and takes the last PPermanent value.

A type for configuring the listening address of the postgres process. postgres can listen on several types of sockets simulatanously but we don't support that behavior. One can either listen on a IP based socket or a UNIX domain socket.

The monoidial version of SocketClass. Used to combine overrides with defaults when creating a SocketClass. The monoid instance treats 'PUnixSocket mempty' as mempty and combines the

The monoidial version of ProcessConfig. Used to combine overrides with defaults when creating a ProcessConfig.

ProcessConfig contains the configuration necessary for starting a process. It is essentially a stripped down CreateProcess.

PartialPostgresPlan

PostgresPlan is used be startPostgresProcess to start the postgres and then attempt to connect to it.

The output of calling startPostgresProcess.

The monoidial version of Plan. Used to combine overrides with defaults when creating a plan.

Plan is the low level configuration necessary for creating a database starting postgres and creating a database. There is no validation done on the Plan. It is recommend that one use the higher level functions such as start which will generate plans that are valid. Plans are used internally but are exposed if the higher level plan generation is not sufficent.