Commita243569

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 Englishword.Author: Álvaro HerreraDiscussion:https://postgr.es/m/CAHut+Pv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w@mail.gmail.com

1 parent8d9978a commita243569Copy full SHA for a243569

File tree

-0

lines changed

-0

lines changed

Lines changed: 8 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -538,6 +538,14 @@ Hint: The addendum, written as a complete sentence.`
`538`	`538`	`variables that will not contain words (for example, operator names).`
`539`	`539`	`</para>`
`540`	`540`
	`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`	`+`
`541`	`549`	`<para>`
`542`	`550`	`There are functions in the backend that will double-quote their own output`
`543`	`551`	`as needed (for example, <function>format_type_be()</function>). Do not put`

Comments

(0)