Building from source#

!!!Warning This option is intended for developers and advanced users. Only software built and tested by EDB is supported by EDB. Please refer to Self-Managed Supported Open Source Software .

You can even combine packaged installations of certain components with source builds of others. For example, you can install Postgres from packages and compile pglogical and PGD from source. However, package dependencies prevent installing pglogical from source and PGD from packages.

Source builds are meant for use in development, testing, and for support operations.

Quick start#

Set up a cluster with 2ndQPostgres, pglogical3, and bdr all built from stable branches:

$ tpaexec configure ~/clusters/speedy -a BDR-Always-ON          \
    --layout bronze                                             \
    --harp-consensus-protocol etcd                              \
    --install-from-source                                       \
      2ndqpostgres:2QREL_13_STABLE_dev                          \
      pglogical3:REL3_7_STABLE                                  \
      bdr3:REL3_7_STABLE

On Socker clusters, you can also build components from local work trees instead of a remote git repository:

$ tpaexec configure ~/clusters/speedy                           \
    --architecture BDR-Always-ON --layout bronze                \
    --harp-consensus-protocol etcd                              \
    --platform docker                                           \
    --install-from-source 2ndqpostgres:2QREL_13_STABLE_dev      \
      pglogical3 bdr3                                           \
    --local-source-directories                                  \
      pglogical3:~/src/pglogical bdr3:~/src/bdr

After deploying your cluster, you can use tpaexec deploy … --skip-tags build-clean on subsequent runs to reuse build directories. Otherwise, the build directory is emptied before starting the build.

BDR, and other components with custom locations and build parameters.

Configuration#

There are two aspects to configuring source builds.

If you want a cluster running a particular combination of sources, run tpaexec configure to generate a configuration with sensible defaults to download, compile, and install the components you select. You can build Postgres or Postgres Extended, pglogical, and BDR and specify branch names to build from, as shown in the examples in Quick start .

The underlying mechanism is capable of much more than the command-line options allow. By editing config.yml , you can clone different source repositories, change the build location, specify different configure or build parameters, redefine the build commands entirely, and so on. You can, therefore, build things other than Postgres, pglogical, and BDR.

For the available options, see:

Building Postgres from source
Building extensions with `install_from_source <Installing from source>`

Local source directories#

You can use TPA to provision Docker containers that build Postgres and extensions from your local source directories instead of from a Git repository.

Suppose you’re using --install-from-source to declare what you want to build:

$ tpaexec configure ~/clusters/speedy                           \
    --architecture BDR-Always-ON --layout bronze                \
    --harp-consensus-protocol etcd                              \
    --platform docker                                           \
    --install-from-source 2ndqpostgres:2QREL_13_STABLE_dev      \
      pglogical3:REL3_7_STABLE bdr3:REL3_7_STABLE               \
      …

By default, this command results in a cluster configuration that cases tpaexec deploy to clone the known repositories for Postgres Extended, pglogical3, and bdr3, checks out the given branches, and builds them. But you can add --local-source-directories to specify that you want the sources to be taken directly from your host machine instead:

$ tpaexec configure ~/clusters/speedy                           \
    --architecture BDR-Always-ON --layout bronze                \
    --harp-consensus-protocol etcd                              \
    --platform docker                                           \
    --install-from-source 2ndqpostgres:2QREL_13_STABLE_dev      \
      pglogical3 bdr3                                           \
    --local-source-directories                                  \
      pglogical3:~/src/pglogical bdr3:~/src/bdr                 \
    …

This configuration installs Postgres Extended from the repository, but obtains pglogical3 and bdr3 sources from the given directories on the host. These directories are bind-mounted read-only into the Docker containers at the same locations where the git repository would have been cloned to, and the default (out-of-tree) build proceeds as usual.

If you specify a local source directory for a component, you can’t specify a branch to build (see pglogical3:REL3_7_STABLE versus plogical3 for --install-from-source in the previous examples). The source directory is mounted read-only in the containers, so TPA can’t use git pull or git checkout to update it. You get whichever branch is checked out locally, including any uncommitted changes.

Using --local-source-directories includes a list of Docker volume definitions in config.yml :

local_source_directories:
  - /home/ams/src/pglogical:/opt/postgres/src/pglogical:ro
  - /home/ams/src/bdr:/opt/postgres/src/bdr:ro
  - ccache-bdr_src_36-20200828200021:/root/.ccache:rw

ccache#

TPA installs ccache by default for source builds of all kinds. When you’re using a Docker cluster with local source directories, by default a new Docker volume is attached to the cluster’s containers to serve as a shared ccache directory. This volume is completely isolated from the host and is removed when the cluster is deprovisioned.

Use the --shared-ccache /path/to/host/ccache configure option to specify a longer-lived shared ccache directory. This directory is bind-mounted read-write into the containers, and its contents are shared between the host and the containers.

(By design, there’s no way to install binaries compiled on the host directly into the containers.)

Rebuilding#

After deploying a cluster with components built from source, run tpaexec rebuild-sources to quickly rebuild and redeploy just those components. This command is faster than running tpaexec deploy but doesn’t apply any configuration changes.

Building from source

Contents