Though many know about streaming replication, I would like to start from Prerequisites and with some Introduction about this replication as this blog is for beginners :-).
Prerequisites:
1. Same version of the PostgreSQL Database must be installed on both servers.
2. Configure the Password-less ssh authentication to use the “postgres” user.
3. Production server must operate in WAL archiving enabled mode by setting archive_mode and archive_command in postgresql.conf file.
4. Production and stand by servers always should have connectivity between them to transfer the archived WAL files from production.
5. Set up your standby host’s environment and directory structure exactly the same as your primary.
Introduction:
It is an asynchronous mechanism; the standby server lags behind the master. But unlike other replication methods, this lag is very short, and can be as little as a single transaction, depending on network speed, database activity, and Streaming replication settings. Also, the load on the master for each slave is minimal, allowing a single master to support dozens of slaves. The feature is included in Postgresql-9.0, with this the second database instance (normally on a separate server) replaying the primary’s binary log, while making that standby server can accept read-only queries.
Here are the practical steps with necessary commands:
1. Connect to Master and create a “replication” user with replication privilege.
$ psql
Password for user postgres:
psql.bin (9.2.1) Type “help” for help.
postgres=# create user replication with replication password ”;
2. We need to change some parameters in postgresql.conf and authentication in pg_hba.conf which are located at /opt/PostgreSQL92/data/ location on Master. Set up connections and authentication so that the standby server can successfully connect to the replication pseudo-database on the primary.
$ $EDITOR postgresql.conf
listen_addresses = ‘*’
$ $EDITOR pg_hba.conf
#The standby server must have superuser access privileges.
host replication replication 10.176.0.0/16 md5
3. Set up the streaming replication related parameters on the primary server.
$EDITOR postgresql.conf
#To enable read¬only queries on a standby server, wal_level must be set to “hot_standby”. But you can choose “archive” if you never connect to the server in standby mode.
wal_level = hot_standby
#Set the maximum number of concurrent connections from the standby servers.
max_wal_senders = 5
#To prevent the primary server from removing the WAL segments required for the standby server before shipping them, set the minimum number of segments retained in the pg_xlog directory.
wal_keep_segments = 32
#Enable WAL archiving on the primary to an archive directory accessible from the standby. If wal_keep_segments is a high enough number to retain the WAL segments required for the standby server, this may not be necessary.
archive_mode = on
Note: Restart the cluster after modifying the above parameters in postgresql.conf file.
4. Re-start postgres on the primary server and check if the parameters are affected.
postgres=# show archive_command ;
archive_command
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ —————–
cp %p /var/PG92_Archives/%f
(1 row)
postgres=# show archive_mode ;
archive_mode
¬¬¬¬¬¬¬¬¬¬¬¬¬¬————-
on
(1 row)
postgres=# show wal_level ;
wal_level
¬¬¬¬¬¬¬¬¬¬¬¬¬————
hot_standby
(1 row)
postgres=# show max_wal_senders ;
max_wal_senders
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬—————-
5
(1 row)
postgres=# show wal_keep_segments ;
wal_keep_segments
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬——————
32
5. Make a base backup of Master server’s data directory.
$ psql ¬c “SELECT pg_start_backup(‘label’, true)”
$ cp /opt/PostgreSQL92/data/* backup/
$psql ¬c “SELECT pg_stop_backup()”
— tar the backup directory and move to standby location.
$tar ¬cvzf backup.tar backup/
6. Move the slave data directory contents to any other location, untar the backup file and copy contents to slave data directory.
7. Set up replication-related parameters, connections and authentication in the standby server like the primary, so that the standby might work as a primary after failover. 8. Enable read-only queries on the standby server. But if wal_level is archive on the primary, leave hot_standby unchanged (i.e., off).
$ $EDITOR postgresql.conf
hot_standby = on
9. Create a recovery command file in the standby server; the following parameters are required for streaming replication.
$ $EDITOR recovery.conf
# Specifies whether to start the server as a standby. In streaming
# replication, this parameter must to be set to on.
standby_mode = ‘on’
# Specifies a connection string which is used for the standby server to
# connect with the primary.
primary_conninfo = ‘host=10.176.112.188 port=5432 user=replication
password= application=’
# Specifies a trigger file whose presence should cause streaming
# replication to end (i.e., failover).
trigger_file = ” ===> Do not create the file. You have to
create the file when failover.
# Specifies a command to load archive segments from the WAL archive. If
# # wal_keep_segments is a high enough number to retain the WAL segments
# # required for the standby server, this may not be necessary. But
# a large workload can cause segments to be recycled before the standby
# is fully synchronized, requiring you to start again from a new base
# backup.
restore_command = ‘cp %f “%p”‘
10. Start postgres in the standby server. It will start streaming replication and you will see log messages like below:
LOG: entering standby mode
LOG: consistent recovery state reached at 0/1D000078
LOG: record with zero length at 0/1D000078
LOG: streaming replication successfully connected to primary
11. You can calculate the replication lag by comparing the current WAL write location on the primary with the last WAL location received/replayed by the standby. They can be retrieved using pg_current_xlog_location function on the primary side and the pg_last_xlog_receive_location or pg_last_xlog_replay_location function on the standby, respectively.
$ psql ¬c “SELECT pg_current_xlog_location()” ¬h192.168.0.10
(primary host)
pg_current_xlog_location
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
0/2000000
(1 row)
$ psql ¬c “select pg_last_xlog_receive_location()” ¬h192.168.0.20
(standby host)
pg_last_xlog_receive_location
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
0/2000000
(1 row)
$ psql ¬c “select pg_last_xlog_replay_location()” ¬h192.168.0.20
(standby host)
pg_last_xlog_replay_location
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
0/2000000
(1 row)
12. Other ways to check streaming replication: the easiest way is “select now()-pg_last_xact_replay_timestamp();” at slave side. pg_last_xact_replay_timestamp() function gives time stamp of last transaction replayed during recovery, time at which the commit or abort WAL record for that transaction was generated on the primary. If no transactions have been replayed during recovery, this function returns NULL. Otherwise, if recovery is still in progress this will increase monotonically. If recovery has completed then this value will remain static at the value of the last transaction applied during that recovery. When the server has been started normally without recovery the function returns NULL. You can try with some operation on Master and then check the fuction output.
If you want to check the delay manually, then go for below steps:
Step 1:Need to create table on Primary using below command.
create table stream_delay (tstamp timestamp without time zone );
insert into stream_delay select now();
Step 2: schedule the below command on primary to execute every minute on cronjob.
update stream_delay set tstamp=’now()’;
step 3: verify the delay on slave by selecting the “stream_delay” table.
It should show the last time that was updated in primary. Difference between this timestamp and current timestamp of slave server shows the time delay between Primary and slave.
You can also check the progress of streaming replication by using ps command.#The displayed LSNs indicate the byte position that the standby server has written up to in the xlogs.
[primary] $ ps ¬ef | grep sender
postgres 6879 6831 0 10:31 ? 00:00:00 postgres: wal sender
process postgres 127.0.0.1(44663) streaming 0/2000000
[standby] $ ps ¬ef | grep receiver
postgres 6878 6872 1 10:31 ? receiver process streaming 0/2000000
Thanks all, Kindly let me know if I miss anything.
postgres 
