Re: Consistently use "startup process"/"WAL sender" instead of "Startup process"/"WAL Sender" in comments and docs. - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Consistently use "startup process"/"WAL sender" instead of "Startup process"/"WAL Sender" in comments and docs.
Date
Msg-id CALj2ACXpHn0Hbm2zDiGr96WD7pC6etqupJwn47pxxeptSaOmTg@mail.gmail.com
Whole thread Raw
In response to Re: Consistently use "startup process"/"WAL sender" instead of "Startup process"/"WAL Sender" in comments and docs.  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: Consistently use "startup process"/"WAL sender" instead of "Startup process"/"WAL Sender" in comments and docs.  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers
On Sun, Feb 13, 2022 at 5:49 PM John Naylor
<john.naylor@enterprisedb.com> wrote:
>
> On Sun, Feb 13, 2022 at 3:13 PM Bharath Rupireddy
> <bharath.rupireddyforpostgres@gmail.com> wrote:
> >
> > Hi,
> >
> > In the code comments, it is being used as "Startup process" in the
> > middle of the sentences whereas in most of the places "startup
> > process" is used. Also, "WAL Sender" is being used instead of "WAL
> > sender". Let's be consistent across the docs and code comments.
>
> FWIW, docs need to hold to a higher standard than code comments.

Thanks. In general, I agree that the docs and error/log messages
(user-facing) need to be of higher standard, but at the same time code
comments too IMHO. Because many hackers/developers consider code
comments a great place to learn the internals, being consistent there
does no harm.

Regards,
Bharath Rupireddy.



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: buildfarm warnings
Next
From: Thomas Munro
Date:
Subject: Re: Add client connection check during the execution of the query