Content-Type: text/plain; charset="utf-8"
Date: Thu, 17 Jan 2013 23:39:53 -0500
From: "Kevin Grittner" <kgrittn@mail.com>
Message-ID: <20130118043953.108970@gmx.com>
MIME-Version: 1.0
Subject: Re: Question concerning replicated server using streaming
	replication used as a read-only reporting server
To: "Benjamin Krajmalnik" <kraj@servoyant.com>,pgsql-admin@postgresql.org
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin