Quick Links

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

From:	"Kevin Grittner" <kgrittn(at)mail(dot)com>
To:	"Benjamin Krajmalnik" <kraj(at)servoyant(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:39:53
Message-ID:	20130118043953.108970@gmx.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-admin

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:

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

	From	Date	Subject
Next Message	Benjamin Krajmalnik	2013-01-18 04:49:33	Re: Question concerning replicated server using streaming replication used as a read-only reporting server
Previous Message	Benjamin Krajmalnik	2013-01-18 02:46:05	Re: Question concerning replicated server using streaming replication used as a read-only reporting server