Page Comparison

...

...

1. The method used for creating the DR cluster (WAL Streaming)

2. The replication user that is used for streaming connection to the primary cluster. By default, the Postgres user is used. It is recommended to use a different user for establishing this connection. Sample user creation SQL used. SUPERUSER role needed here because only SUPERUSER can retrieve the pg_read_all_statsrole needed for the user because retrieving streaming sync status between primary database and standby database requires pg_read_all_stats access. Sample user creation SQL used

create user repuser replication login encrypted password 'xxxxxx';
alter ROLEGRANT pg_read_all_stats TO repuser SUPERUSER;

3. The password of the replication user that is used for streaming connection to the primary cluster.

4. A replication test that can be done to ensure the correct username and password with necessary privileges and the whether the pg_hba.conf updates are correct.

5. The result of the replication test.

6. By, default the observer is enabled that will start monitoring the configuration as soon the DR cluster is created.

7. Click start to start creating the DR cluster using WAL streaming method.

...

...

...

-bash-4.2$ ls -lrt /u01
drwx------ (or drwxr-x---).  5 postgres postgres  4096 Aug 16 16:41 tablespace
drwx------ (or drwxr-x---). 20 postgres postgres  4096 Aug 26 12:06 PG5433-12

5. The location of the configuration files (postgresql.conf, pg_hba.conf, and pg_indent.conf). This location can be different from the primary data directory, but the example below has these two in the same directory. Keeping the same as the primary is recommended, but this can also be different in the standby. postgresql.conf, pg_hba.conf, and pg_indent.conf need to be placed in the same folder.

6. For this example, a Hot standby is created that can be accessible for reporting purposes as the databases in the cluster are in read only mode.

...