Wording variations in descriptions of gucs.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Wording variations in descriptions of gucs.
Date: 2019-06-07 08:06:09
Message-ID: CAKPRHzKbGzGgun7yMqYmztvGHwm4otk4+ejXS7BcHxOKm_EQgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello.

In guc.c many of the variables are described as "Set_s_ something"
as if the variable name is the omitted subject. A few seem being
wrongly written as "Set something" with the same intention.

Is it useful to unify them to the majority?

wal_level
> gettext_noop("Set the level of information written to the WAL."),

log_transaction_sample_rage
> gettext_noop("Set the fraction of transactions to log for new transactions."),

Though, recovery_target seems written as intended.

> gettext_noop("Set to 'immediate' to end recovery as soon as a consistent state is reached.

# rather it seems to be the detaied description..

regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
guc_desc_fix.patch application/octet-stream 960 bytes

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2019-06-07 08:11:45 Re: tableam: abstracting relation sizing code
Previous Message Daniel Gustafsson 2019-06-07 07:52:26 Re: be-gssapi-common.h should be located in src/include/libpq/