Wording variations in descriptions of gucs. - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Wording variations in descriptions of gucs.
Date
Msg-id CAKPRHzKbGzGgun7yMqYmztvGHwm4otk4+ejXS7BcHxOKm_EQgQ@mail.gmail.com
Whole thread Raw
List 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

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: be-gssapi-common.h should be located in src/include/libpq/
Next
From: Daniel Gustafsson
Date:
Subject: Re: tableam: abstracting relation sizing code