From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Consistently use "startup process"/"WAL sender" instead of "Startup process"/"WAL Sender" in comments and docs. |
Date: | 2022-02-14 04:11:52 |
Message-ID: | CALj2ACXpHn0Hbm2zDiGr96WD7pC6etqupJwn47pxxeptSaOmTg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Feb 13, 2022 at 5:49 PM John Naylor
<john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Sun, Feb 13, 2022 at 3:13 PM Bharath Rupireddy
> <bharath(dot)rupireddyforpostgres(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2022-02-14 04:15:05 | Re: Add client connection check during the execution of the query |
Previous Message | Thomas Munro | 2022-02-14 02:29:08 | Re: buildfarm warnings |