Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit a243569

Browse filesBrowse files
committed
doc: Mention how to use quotes with GUC names in error messages
Quotes should not be used except if a GUC name is a natural English word. Author: Álvaro Herrera Discussion: https://postgr.es/m/CAHut+Pv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w@mail.gmail.com
1 parent 8d9978a commit a243569
Copy full SHA for a243569

File tree

Expand file treeCollapse file tree

1 file changed

+8
-0
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+8
-0
lines changed
Open diff view settings
Collapse file

‎doc/src/sgml/sources.sgml‎

Copy file name to clipboardExpand all lines: doc/src/sgml/sources.sgml
+8Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -538,6 +538,14 @@ Hint: The addendum, written as a complete sentence.
538538
variables that will not contain words (for example, operator names).
539539
</para>
540540

541+
<para>
542+
In messages containing configuration variable names, do not include quotes
543+
when the names are visibly not natural English words, such as when they
544+
have underscores, are all-uppercase or have mixed case. Otherwise, quotes
545+
must be added. Do include quotes in a message where an arbitrary variable
546+
name is to be expanded.
547+
</para>
548+
541549
<para>
542550
There are functions in the backend that will double-quote their own output
543551
as needed (for example, <function>format_type_be()</function>). Do not put

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.