Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dgGS3-0003aA-6V for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 20:22:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dgGS2-00045r-PN for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 20:22:34 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dgGRf-0002mN-H4 for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 20:22:11 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dgGRc-0003dL-UH for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 20:22:10 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0EA6F20D28; Fri, 11 Aug 2017 16:22:08 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 11 Aug 2017 16:22:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=RFcEqxwDbPK+wTSyItb2jh+4oKBORT/lSJByTE92vuw=; b=VTHPbASH Uih1XnJfmsisODMWvgQjzeA7hk8XdpQGnhIkoAU8bu63njJ1jOai1hptlE1eN0eE ACRic0gI0e6pzTmAI0740Zyr594EZ8YLb5Cwj3hIwI46l1YJUPuJ/LnF7iN8I8O2 hU/CsCt1MECiBFwvdiiUWibW0VsPZpP8xAa5TG7UrFWmF8uVtWvsj0tppIseodRd h0dYqC/ugcQylsOZYlKOqsBV6vAUQ1B0UtA96cPe+A0oKfQHoh1XvAYthWBX7T8n 6IMa78ErjbF0MySL2u1MwRjfJQeC1Zgzl34phWMNWiIg+ie8b2/Rv5itoHHuEiBq oWVvtWKfhqW9dw== X-ME-Sender: X-Sasl-enc: wx/6a94HwsnNxBnO446myDx/8+zs3Nwwcz61Yglnh2ni 1502482927 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id C457D24442; Fri, 11 Aug 2017 16:22:07 -0400 (EDT) Subject: Re: obsolete description for rolreplication in pg_authid and pg_roles To: Fujii Masao , pgsql-docs References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <1fb2102a-c5ec-6777-1a73-81c8f3698409@2ndquadrant.com> Date: Fri, 11 Aug 2017 16:22:07 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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 3/21/17 15:00, Fujii Masao wrote: > catalog.sgml >> That is, this role can initiate streaming replication (see Section >> 26.2.5, “Streaming Replication”) and set/unset the system backup >> mode using pg_start_backup and pg_stop_backup > > The latter part of the above description for rolreplication column seems > obsolete because commit 1574783b4ced0356fbc626af1a1a469faa6b41e1 > changed pg_start_backup and pg_stop_backup so that GRANT system > is used to manage access to those functions. So I think that we should > get rid of the latter part or replace it with something like "run pg_basebackup > to take a base backup". Thought? fixed -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs