Re: primary/secondary/master/slave/standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: primary/secondary/master/slave/standby
Date
Msg-id AANLkTik2YLK6Fhd8x5kcVx8ZdE9sAJkWVYObZ2epT6zy@mail.gmail.com
Whole thread Raw
In response to Re: primary/secondary/master/slave/standby  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Wed, May 12, 2010 at 5:44 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Tom Lane wrote:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>> > The server's messages and the documentation uses all of these terms in
>> > mixed ways.  Maybe we could decide on some preferred terminology and
>> > adjust the existing texts.  Ideas?
>>
>> Primary/secondary seem like a poor choice because they're such generic
>> terms.  Master/slave is the common terminology for this, I think,
>> though some might object on grounds of political incorrectness.
>> If so, master/standby would probably work.
>
> I have always been unclear if a slave indicates it accepts read-only
> queries, i.e. are slave and standby interchangable?

We had a long discussion of this topic last summer:

http://archives.postgresql.org/pgsql-hackers/2009-08/msg00870.php

I still think Peter's right, but there were contrary opinions.  Still,
the discussion is an interesting read.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: primary/secondary/master/slave/standby
Next
From: Robert Haas
Date:
Subject: recovery getting interrupted is not so unusual as it used to be