From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: outdated references to replication timeout |
Date: | 2021-01-13 13:51:35 |
Message-ID: | CAFBsxsE0iun4dOiTyBmHpsrzor40s=Vw-Ap2cSjxvTWsLwDoWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 12, 2021 at 9:37 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> Thanks for the patch! I think this change makes sense.
>
> - (errmsg("terminating walsender process
> due to replication timeout")));
> + (errmsg("terminating walsender process
> due to WAL sender timeout")));
>
> Isn't it a bit strange to include different expressions "walsender" and
> "WAL sender" for the same thing in one message?
It is strange, now that I think about it. My thinking was that the former
wording of "replication timeout" was a less literal reference to the
replication_timeout parameter, so I did the same for wal_sender_timeout. A
quick look shows we are not consistent in the documentation as far
as walsender vs. WAL sender. For the purpose of the patch I agree it should
be consistent within a single message. Maybe the parameter should be
spelled exactly as is, with underscores? I'll take a broader look and send
an updated patch.
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2021-01-13 13:59:20 | Re: Alter timestamp without timezone to with timezone rewrites rows |
Previous Message | Alexey Kondratov | 2021-01-13 13:39:40 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |