From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: primary/secondary/master/slave/standby |
Date: | 2010-05-12 21:44:32 |
Message-ID: | 201005122144.o4CLiW501587@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-05-12 21:55:24 | Re: pg_upgrade versus MSVC build scripts |
Previous Message | Bruce Momjian | 2010-05-12 21:42:47 | Re: [COMMITTERS] pgsql: Add PGFILEDESC description to Makefiles for all /contrib |