Re: Live steraming replication setup issue! - Mailing list pgsql-general

From Venkata Balaji N
Subject Re: Live steraming replication setup issue!
Date
Msg-id CAEyp7J_ajkURnndSkH3fh+H5JKYvn854RvARaEoFNsg_pcQ5+A@mail.gmail.com
Whole thread Raw
In response to Re: Live steraming replication setup issue!  (Ashish Chauhan <Ashish.Chauhan@support.com>)
Responses Re: Live steraming replication setup issue!  (Ashish Chauhan <Ashish.Chauhan@support.com>)
List pgsql-general

On Fri, Feb 19, 2016 at 6:24 PM, Ashish Chauhan <Ashish.Chauhan@support.com> wrote:
Below is recovery.conf on slave

#---------------------------------------------------------------------------
# STANDBY SERVER PARAMETERS
#---------------------------------------------------------------------------
#
# standby_mode
#
# When standby_mode is enabled, the PostgreSQL server will work as a
# standby. It will continuously wait for the additional XLOG records, using
# restore_command and/or primary_conninfo.
#
standby_mode = 'on'
#
# primary_conninfo
#
# If set, the PostgreSQL server will try to connect to the primary using this
# connection string and receive XLOG records continuously.
#
primary_conninfo = 'host=<master server ip> port=5432'
#
#
# By default, a standby server keeps restoring XLOG records from the
# primary indefinitely. If you want to stop the standby mode, finish recovery
# and open the system in read/write mode, specify path to a trigger file.
# The server will poll the trigger file path periodically and start as a
# primary server when it's found.
#
trigger_file = '/data/main/primary.trigger'

Can you consider putting recovery_target_timeline='latest' as well ? and can you help us know if you can see anything weird in the postgresql logfiles @ DR ?

Is DR in complete sync with the slave ?

Regards,
Venkata B N

Fujitsu Australia

pgsql-general by date:

Previous
From: "Peter J. Holzer"
Date:
Subject: Re: BRIN Usage
Next
From: Kevin Waterson
Date:
Subject: ERROR: missing FROM-clause entry for table