Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcdE8-00014v-7k for pgsql-docs@arkaria.postgresql.org; Tue, 01 Aug 2017 19:53:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dcdE7-0007Wj-Qt for pgsql-docs@arkaria.postgresql.org; Tue, 01 Aug 2017 19:53:11 +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 1dcdE6-0007S8-Hb for pgsql-docs@postgresql.org; Tue, 01 Aug 2017 19:53:10 +0000 Received: from mail-qk0-x230.google.com ([2607:f8b0:400d:c09::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dcdE2-0005EG-Ry for pgsql-docs@postgresql.org; Tue, 01 Aug 2017 19:53:10 +0000 Received: by mail-qk0-x230.google.com with SMTP id d145so15532377qkc.2 for ; Tue, 01 Aug 2017 12:53:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=0PHq9jmkPatnYeJJuWZ4RlYMSduJqNVWqsoC6nUq8lI=; b=hNvjB3xyBf/7fhwpLo+YKIk/CZ+jZCyN9ivQbL9mzvns5KQcih9cF9R+wBpHrhH6qi j+c00Np/cbLOIxY07PGeyHocwDrH2b3KSJbym1XlfOVRn82lid64g50ftaJjQYMdjfpa eX4RjXsvgSsVwZeoYiytzWVbN0uLNU1b9czuvbbgTjgszqHor7Jjo6FWWxZQ6nKQ3XNs 0o5tC2oP3hjdb5exfkyjUqv9B2/ir5pPiSK/+cDBb3ru9w2L9jlYXjukxHJeEp5FC5Bv UO8NAaB2Z7i0mQRPkd3cAC0jifweAnhCPJDeGbruQmXzIU8/0O7494EBaOUIjPcJirY6 7OXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=0PHq9jmkPatnYeJJuWZ4RlYMSduJqNVWqsoC6nUq8lI=; b=L87vXpWaeMKkUS/IOysLNSFlcGOPaK91yLPY+YmDbYXnKfmtUddyPPmZjFBAV3ouNE 1o0jTB3ra/LoVbiDNXu/7hx4FnRM8NI1cJYwL73XhPfu7vvStPNm2NLrGMHSeiwhXn/h /a1g8jmd/OlbLTRh+1BT9BXObc3KqLUywOvoprkJ9jsZCK9mhx3CMVFbXl172CqSv74M CryYtsZIL9sKsMTyXizaN6F6cFGyZKHTFz4diJtmhxx0K0dJpursKfNhgnjAPb1EDrIN eUtI3QA7L+d5TJ/xiQ8qEs5kZPuPd+t77E0SuhADcVsrRizedYvLdmv4cqxkKWK+q/4K xq2Q== X-Gm-Message-State: AIVw112axkXdFr+vYBFuAfKsAWlvw8MeGLpqqTEjhaXlHpdnY2FQz1v+ 4rqKR9HR98hoL/ha X-Received: by 10.55.97.13 with SMTP id v13mr28562100qkb.107.1501617185123; Tue, 01 Aug 2017 12:53:05 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([179.57.115.10]) by smtp.gmail.com with ESMTPSA id n57sm797087qtf.74.2017.08.01.12.53.04 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 01 Aug 2017 12:53:04 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id D40BD11ED; Tue, 1 Aug 2017 15:53:01 -0400 (-04) Date: Tue, 1 Aug 2017 15:53:01 -0400 From: Alvaro Herrera To: Simon Riggs Cc: sabrina.iqbal@target.com, pgsql-docs@postgresql.org Subject: Re: Use of term Master/Slave Message-ID: <20170801195301.yqyzifsxv7zq23gp@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) 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 Simon Riggs wrote: > On 31 July 2017 at 22:13, 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. > > Do you think primary/secondary is more descriptive? I think "primary" is fine, but "secondary" isn't. > I started using the terms Primary and Secondary in the original use, > but I think we've moved away from that towards Master/Standby, which > fits better with a world where "muti-master" is a frequently used term > and an eventual goal in core. Multi-primary doesn't seem to make much > sense. Elsewhere we've started using the terms "origin" and "replica". "Multi-origin" sounds sensible enough to me whereas "multi-primary" doesn't. -- Álvaro Herrera https://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