Re: [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration?
От | Bruce Momjian |
---|---|
Тема | Re: [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration? |
Дата | |
Msg-id | 20140910202002.GA21173@momjian.us обсуждение исходный текст |
Ответ на | Re: [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration? (David Johnston <david.g.johnston@gmail.com>) |
Ответы |
Re: [9.3] Should we mention "set_config(...)" in 18.1.3 in
Server Configuration?
|
Список | pgsql-docs |
On Tue, Sep 9, 2014 at 03:40:45PM -0400, David Johnston wrote: > Minor corrections: > > First block: " > In the first section of this chapter, we > describe how to set configuration parameters" > > - remove the comma > > Second Block: > - placement of the colon inside or outside of the emphasis tag is inconsistent > (string, unit, enum are inside; boolean and numeric are outside) > - units: "An numeric value..." -> maybe "An unadorned numeric value... > > Third block: > "Hash marks (<literal>#</literal>) designate the remainder of lines as > comments." -> "...designate the remainder of the line as a comment." I read > this at first as "remaining lines [in the file] ... " > > "To embed a single quote in a parameter value, write either two quotes > (preferred) or backslash-quote." -> remove the comma > "Querying this view is the sames as" -> "the same as" I agree all of the above are improvements, and changed. > "In addition to setting global defaults or attaching" <- add a comma after > "defaults" I didn't like this change as it causes too many comma phrases. Attaches are the changes since yesterday's patch. The full patch is at: ftp://momjian.us/postgresql/mypatches/config.diff -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
Вложения
В списке pgsql-docs по дате отправления: