Re: pg_standby replication problem

From: Khangelani Gama <kgama(at)argility(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_standby replication problem
Date: 2014-06-10 05:02:28
Message-ID: 630fc57207fe0796ff63cfe3ae4c3a09@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)aklaver(dot)com]
Sent: Tuesday, June 10, 2014 1:42 AM
To: Khangelani Gama; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] pg_standby replication problem

On 06/09/2014 11:15 AM, Khangelani Gama wrote:
> This is the standby replication setting with archive_command sending
> the WALs from master to standby.
>
>

Thanks for feedback from everyone, I will try and remove the correct old
walfiles.

What are the conf settings on the standby server?

Standby server config settings are as follows:

# WRITE AHEAD LOG
#------------------------------------------------------------------------------

# - Settings -

wal_level = archive
#wal_level = minimal # minimal, archive, or hot_standby
# (change requires restart)
#fsync = on # turns forced synchronization on or
off
synchronous_commit = off # synchronization level; on, off, or
local
#wal_sync_method = fsync

# - Checkpoints -

checkpoint_segments = 128
checkpoint_timeout = 15min
checkpoint_warning = 885s
#checkpoint_segments = 3

# - Archiving -

archive_mode = on
#archive_mode = off # allows archiving to be done
# (change requires restart)

# REPLICATION
#------------------------------------------------------------------------------

# - Master Server -

# These settings are ignored on a standby server

max_wal_senders = 3 # max number of walsender processes
# (change requires restart)

# This is used when logging to stderr:
logging_collector = on
#logging_collector = off

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

CONFIDENTIALITY NOTICE
The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential
information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by anyone
other than the intended addressee is prohibited.If you are not the intended addressee please notify the writer immediately
and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no liability
for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bhushan Pathak 2014-06-10 10:30:31 Re: PostgreSQL 9.2.4 + CentOS 6.5 64 bit - segfault error in initdb
Previous Message Jonathan Vanasco 2014-06-10 00:55:01 two questions about fulltext searchign / tsvector indexes