Using additional configuration options

The walbouncer tool can do a lot more for users than has been outlined so far. A couple of additional configuration parameters are available.

The first example shows what can be done if more than one slave is around:

listen_port: 5433
master:
    host: localhost
    port: 5432
configurations:
    - slave1:
        match:
            application_name: slave1
        filter:
            include_tablespaces: [spc_slave1]
            exclude_databases: [test]

Inside the configuration block, there is the slave1 section. The slave1 configuration will be chosen if a slave connects itself using slave1 as application_name (as outlined in the application_name clause). If this configuration is chosen by the server (there can be many such slave sections), the filters listed in the next block are applied. Basically, each type of filter comes in two incarnations: include_ and exclude_. In this example, only the spc_slave1 tablespace is included. The final setting says...