Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XmB3l-0001K6-Gh for pgsql-docs@arkaria.postgresql.org; Thu, 06 Nov 2014 00:36:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XmB3k-00027z-Jh for pgsql-docs@arkaria.postgresql.org; Thu, 06 Nov 2014 00:36:20 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XmB3j-00023T-2w for pgsql-docs@postgresql.org; Thu, 06 Nov 2014 00:36:19 +0000 Received: from mout.gmx.net ([212.227.15.19]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XmB3f-0005Vp-Bk for pgsql-docs@postgresql.org; Thu, 06 Nov 2014 00:36:16 +0000 Received: from auth2-smtp.messagingengine.com ([66.111.4.228]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LnPGI-1YFDTW3fKw-00hebq for ; Thu, 06 Nov 2014 01:36:13 +0100 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailauth.nyi.internal (Postfix) with ESMTP id A3EAC20BB6 for ; Wed, 5 Nov 2014 19:36:11 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 05 Nov 2014 19:36:11 -0500 X-Sasl-enc: evlV7nUZHiXSjR82aVb1imTJFVPUAYBAJ8UKAzT+ZVq2 1415234171 Received: from jesse.mybdev.com (unknown [67.165.24.246]) by mail.messagingengine.com (Postfix) with ESMTPA id 57E28680101; Wed, 5 Nov 2014 19:36:11 -0500 (EST) Message-ID: <545AC27B.1050701@gmx.net> Date: Wed, 05 Nov 2014 19:36:11 -0500 From: Peter Eisentraut User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Michael Paquier CC: pgsql-docs Subject: Re: obsolete pg_receivexlog note? References: <54454F47.50407@gmx.net> <545A99AA.5020107@gmx.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ZPMlySGiMURFoN/T6dNPxEopRdzYMR9/bep6IR3enTDq/8u6ZLL HszUe9Jd6eg14fmckQV9aExo7OY/++mmCtKE50l96lduZHuc1W2u9jefEVPZLU4iwMc6um+ T8YYYJBLkSv7Rk/IQYy04pKCkVUGDH75Cr51J8GxezbkaTi8zxn1XIYYSDLWxu/JmxIHYwc yZpD9LBqX7AmywJWfxS6Q== X-UI-Out-Filterresults: notjunk:1; X-Pg-Spam-Score: -2.5 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 11/5/14 6:54 PM, Michael Paquier wrote: > In this paragraph, is it worth mentioning as well that the tradeoff > when using replication slots is to monitor the xlog partition to be > sure it doesn't get full? Might as well. -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs