| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: language cleanups in code and docs |
| Date: | 2020-07-08 21:17:56 |
| Message-ID: | 20200708211756.GA23569@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jul-08, David Steele wrote:
> On 7/8/20 4:39 PM, Andres Freund wrote:
> I think this phrasing in the original/updated version is pretty awkward:
>
> + A standby server that cannot be connected to until it is promoted to a
> + primary server is called a ...
Yeah.
> How about:
>
> + A standby server that must be promoted to a primary server before
> + accepting connections is called a ...
How about just reducing it to "A standby server that doesn't accept
connection is called a ..."? We don't really need to explain that if
you do promote the standby it will start accept connections -- do we?
It should be pretty obvious if you promote a standby, it will cease to
be a standby in the first place. This verbiage seems excessive.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2020-07-08 21:19:41 | Re: language cleanups in code and docs |
| Previous Message | David Steele | 2020-07-08 21:09:42 | Re: language cleanups in code and docs |