Table of Contents Previous Next


6 Sample BART System with Local and Remote Database Servers : 6.4 WAL Archiving Configuration Parameters

The parameters in the postgresql.conf file to enable WAL archiving are shown by the following.
The postgresql.conf file for the local Advanced Server, ACCTG is set as follows:
When the INIT subcommand is invoked, the Postgres archive_command configuration parameter in the postgresql.auto.conf file will be set based on the BART archive_command parameter located in the BART configuration file:
The postgresql.auto.conf file contains the following after the INIT subcommand is invoked:
The archive_command uses the cp command instead of scp since the BART backup catalog is local to this database cluster and the BART user account owning the backup catalog, enterprisedb, is the same user account running Advanced Server. The result is that there is no directory permission conflict during the archive operation.
The postgresql.conf file for the remote Advanced Server, MKTG is set as follows:
When the INIT subcommand is invoked, the Postgres archive_command configuration parameter in the postgresql.auto.conf file will be set by the default, BART format of the BART archive_command parameter since it is not explicitly set for this database server in the BART configuration file:
The default, BART archive_command format is the following:
The postgresql.auto.conf file contains the following after the INIT subcommand is invoked:
The archive_command uses the scp command since the BART backup catalog is remote relative to this database cluster. The BART user account, enterprisedb, is specified on the scp command since this is the user account owning the BART backup catalog where the archived WAL files are to be copied. The result is that there is no directory permission conflict during the archive operation.
The postgresql.conf file for the remote PostgreSQL server, HR is set as follows:
When the INIT subcommand is invoked, the Postgres archive_command configuration parameter in the postgresql.auto.conf file will be set by the default, BART format of the BART archive_command parameter since it is not explicitly set for this database server in the BART configuration file:
The default, BART archive_command format is the following:
The postgresql.auto.conf file contains the following after the INIT subcommand is invoked:
The archive_command uses the scp command since the BART backup catalog is remote relative to this database cluster. The BART user account, enterprisedb, is specified on the scp command since this is the user account owning the BART backup catalog where the archived WAL files are to be copied. The result is that there is no directory permission conflict during the archive operation.

6 Sample BART System with Local and Remote Database Servers : 6.4 WAL Archiving Configuration Parameters

Table of Contents Previous Next