Re: Question concerning replicated server using streaming replication used as a read-only reporting server

From: "Benjamin Krajmalnik" <kraj(at)servoyant(dot)com>
To: <kgrittn(at)mail(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Question concerning replicated server using streaming replication used as a read-only reporting server
Date: 2013-01-18 04:49:33
Message-ID: 007601cdf537$4170d8bb$fa0014ac@stackdump.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

thx

Sent from my Verizon Wireless 4G LTE smartphone

Kevin Grittner <kgrittn(at)mail(dot)com> wrote:

Benjamin Krajmalnik wrote:

> It is ok if I am a little bit behind. What setting do
> I need to tweak to allow it to get further behind?

The relevant settings are described here:

http://www.postgresql.org/docs/9.0/interactive/runtime-config-wal.html#RUNTIME-CONFIG-REPLICATION
http://www.postgresql.org/docs/9.0/interactive/runtime-config-wal.html#RUNTIME-CONFIG-STANDBY

The ones that you might want to look at are:

vacuum_defer_cleanup_age
max_standby_archive_delay
max_standby_streaming_delay

Leaving some gaps for "catch up time" between long-running requests
can help prevent cancelations, since the lag can otherwise
accumulate.

-Kevin

Browse pgsql-admin by date

  From Date Subject
Next Message Albe Laurenz 2013-01-18 10:09:56 Re: Need assistance in incremental backup for my environment
Previous Message Kevin Grittner 2013-01-18 04:39:53 Re: Question concerning replicated server using streaming replication used as a read-only reporting server