Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw3ty-0002NP-49 for pgsql-admin@arkaria.postgresql.org; Fri, 18 Jan 2013 04:50:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tw3tx-0005c8-52 for pgsql-admin@arkaria.postgresql.org; Fri, 18 Jan 2013 04:50:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw3tw-0005c3-G6 for pgsql-admin@postgresql.org; Fri, 18 Jan 2013 04:50:00 +0000 Received: from [64.207.29.137] (helo=mail.illumen.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tw3ts-00025g-Fj for pgsql-admin@postgresql.org; Fri, 18 Jan 2013 04:50:00 +0000 Received: from 172.20.0.250 ([172.20.0.250]) by fletch.stackdump.local ([172.20.0.250]) with Microsoft Exchange Server HTTP-DAV ; Fri, 18 Jan 2013 04:49:53 +0000 Date: Thu, 17 Jan 2013 21:49:33 -0700 Subject: Re: Question concerning replicated server using streaming replication used as a read-only reporting server Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-ID: <007601cdf537$4170d8bb$fa0014ac@stackdump.local> X-Priority: 3 thread-topic: [ADMIN] Question concerning replicated server using streaming replication used as a read-only reporting server thread-index: Ac31N0FwbWsevN3fQj6FXHBtTLxbRg== X-MimeOLE: Produced By Microsoft Exchange V6.5 From: "Benjamin Krajmalnik" To: , MIME-Version: 1.0 X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.207.29.137 (failed) X-Pg-Spam-Score: -1.1 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org thx Sent from my Verizon Wireless 4G LTE smartphone Kevin Grittner 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#RUNT= IME-CONFIG-REPLICATION http://www.postgresql.org/docs/9.0/interactive/runtime-config-wal.html#RUNT= IME-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 --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin