mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Revise GUC names quoting in messages again
After further review, we want to move in the direction of always quoting GUC names in error messages, rather than the previous (PG16) wildly mixed practice or the intermittent (mid-PG17) idea of doing this depending on how possibly confusing the GUC name is. This commit applies appropriate quotes to (almost?) all mentions of GUC names in error messages. It partially supersedesa243569bf6
and8d9978a717
, which had moved things a bit in the opposite direction but which then were abandoned in a partial state. Author: Peter Smith <smithpb2250@gmail.com> Discussion: https://www.postgresql.org/message-id/flat/CAHut%2BPv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w%40mail.gmail.com
This commit is contained in:
@@ -533,17 +533,10 @@ Hint: The addendum, written as a complete sentence.
|
||||
<title>Use of Quotes</title>
|
||||
|
||||
<para>
|
||||
Always use quotes to delimit file names, user-supplied identifiers, and
|
||||
other variables that might contain words. Do not use them to mark up
|
||||
variables that will not contain words (for example, operator names).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In messages containing configuration variable names, do not include quotes
|
||||
when the names are visibly not natural English words, such as when they
|
||||
have underscores, are all-uppercase or have mixed case. Otherwise, quotes
|
||||
must be added. Do include quotes in a message where an arbitrary variable
|
||||
name is to be expanded.
|
||||
Always use quotes to delimit file names, user-supplied identifiers,
|
||||
configuration variable names, and other variables that might contain
|
||||
words. Do not use them to mark up variables that will not contain words
|
||||
(for example, operator names).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
Reference in New Issue
Block a user