Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dg087-0007n4-MD for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 02:56:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dg087-0000IY-8k for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 02:56:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dg086-0000ID-MO for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 02:56:54 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dg080-0000e3-Uc for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 02:56:54 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 45A7A20766; Thu, 10 Aug 2017 22:56:47 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Thu, 10 Aug 2017 22:56:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=IESr9YE9NgFKC3bQ1C+Soq//gjWBVEgugaNQt0Tsu2c=; b=Er8/spWe 2wdpbPnQNLvXdMkbrZet8b2j5Kc4FTJmVIVo4We3MV+L8Noc6Xz89LYWoT8DQfRD W8jCwXyIT4ccrCJeB9iLC9BjarcR56r69yBe0eC63bH/mup6nhDPgEM9VCy9G28Q ZeZ8atFJ194JEC9BWVtPgIovbcSrr7mEEvuGmFb26YDFUP19Pnnl/7JqH48/ulwm USxvu3fsWR2QTb70HzVyaaC5QErCySdNKEhgRS6mSOusEimMJzO0jgEDBIEU22Ee nbM25nFlc8uMJGc0Z28CEENUW5BpiEs2UEymJQT7t1B22pZaKTmvYjSOO8L0YPHR EZ9kGW50xAZTIw== X-ME-Sender: X-Sasl-enc: H/tFKNSwQ4qZQI6/FNqoSoNR+yeshtSYQkJl4CV4BVc7 1502420207 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 F0A9D2418B; Thu, 10 Aug 2017 22:56:46 -0400 (EDT) Subject: Re: Use of term Master/Slave From: Peter Eisentraut To: Andres Freund , sabrina.iqbal@target.com References: <20170731211348.1449.52678@wrigleys.postgresql.org> <20170801173337.l3ysb2hvxlwgs44j@alap3.anarazel.de> Cc: pgsql-docs@postgresql.org Organization: 2ndQuadrant Message-ID: <9fb42a16-3816-a1f6-162c-43d63db692fc@2ndquadrant.com> Date: Thu, 10 Aug 2017 22:56:46 -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: 7bit 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 8/7/17 17:46, Peter Eisentraut wrote: > On 8/1/17 13:33, Andres Freund wrote: >> On 2017-07-31 21:13:48 +0000, sabrina.iqbal@target.com wrote: >>> The following documentation comment has been logged on the website: >>> >>> Page: https://www.postgresql.org/docs/9.6/static/release-9-6.html >>> Description: >>> >>> Wondering why PostgreSQL still uses the terms master and slave when there >>> are other terms like primary/secondary that can be used in the same manner. >> >> Yea, I think we should be more careful from now on. I think several >> people already try, but it's not been a concerted effort so far. > > Here is a patch to remove remaining uses of "slave" in replication contexts. committed -- 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