1
0
mirror of https://github.com/postgres/postgres.git synced 2025-10-24 01:29:19 +03:00

Code + docs review for escaping of option values (commit 11a020eb6).

Avoid memory leak from incorrect choice of how to free a StringInfo
(resetStringInfo doesn't do it).  Now that pg_split_opts doesn't scribble
on the optstr, mark that as "const" for clarity.  Attach the commentary in
protocol.sgml to the right place, and add documentation about the
user-visible effects of this change on postgres' -o option and libpq's
PGOPTIONS option.
This commit is contained in:
Tom Lane
2015-06-29 12:42:52 -04:00
parent 07cb8b02ab
commit cbc8d65639
5 changed files with 29 additions and 19 deletions

View File

@@ -284,12 +284,18 @@ PostgreSQL documentation
<term><option>-o <replaceable class="parameter">extra-options</replaceable></option></term>
<listitem>
<para>
The command-line-style options specified in <replaceable
The command-line-style arguments specified in <replaceable
class="parameter">extra-options</replaceable> are passed to
all server processes started by this
<command>postgres</command> process. If the option string contains
any spaces, the entire string must be quoted; multiple
option invocations are appended.
<command>postgres</command> process.
</para>
<para>
Spaces within <replaceable class="parameter">extra-options</> are
considered to separate arguments, unless escaped with a backslash
(<literal>\</>); write <literal>\\</> to represent a literal
backslash. Multiple arguments can also be specified via multiple
uses of <option>-o</>.
</para>
<para>