Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XPPpS-0002MM-0T for pgsql-docs@arkaria.postgresql.org; Thu, 04 Sep 2014 05:43:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XPPpR-0007hu-09 for pgsql-docs@arkaria.postgresql.org; Thu, 04 Sep 2014 05:43:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XPPpQ-0007hg-3w for pgsql-docs@postgreSQL.org; Thu, 04 Sep 2014 05:43:28 +0000 Received: from 01.zmailcloud.com ([192.198.85.104] helo=mx-out-1.zmailcloud.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XPPpM-0002zs-48 for pgsql-docs@postgreSQL.org; Thu, 04 Sep 2014 05:43:27 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 8376D5649E3; Thu, 4 Sep 2014 00:43:22 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 67D70A0571; Thu, 4 Sep 2014 00:43:22 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b_taj2bTMraz; Thu, 4 Sep 2014 00:43:22 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 42E17A0579; Thu, 4 Sep 2014 00:43:22 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 18817A0578; Thu, 4 Sep 2014 00:43:22 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id qY5jtFtzJUxH; Thu, 4 Sep 2014 00:43:22 -0500 (CDT) Received: from [10.0.0.165] (c-50-139-39-6.hsd1.or.comcast.net [50.139.39.6]) by smtp-out-1.01.com (Postfix) with ESMTPSA id A9D54A0571; Thu, 4 Sep 2014 00:43:21 -0500 (CDT) Message-ID: <5407FBF7.5070204@agliodbs.com> Date: Wed, 03 Sep 2014 22:43:19 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: pgsql-docs@postgreSQL.org CC: Andres Freund Subject: Missing docs: setting up replication slots for standbys Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) 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 Section 46.2.2 has this: Note: PostgreSQL also has streaming replication slots (see Section 25.2.5), but they are used somewhat differently there. Section 25.2.5 has this: You can avoid this by setting wal_keep_segments to a value large enough to ensure that WAL segments are not recycled too early, or by configuring a replication slot for the standby. ... however, absolutely nowhere is it explained how to configure a replication slot for a streaming replica. Is it, in fact, possible to do so? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs